• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    the modalities of this request provide a configuration method, applied to a communications system. the communications system includes a master node and a secondary node that jointly provide a service for a terminal. the method includes: generating, by the secondary node, configuration information for a signaling radio carrier (srb), where the srb is used to transmit a radio resource control (rrc) message between the secondary node and the terminal; send, through the secondary node, the configuration information from the srb to the master node, so that the configuration information from the srb is sent to the terminal through the master node; and receive, by the secondary node, a result of configuring the srb through the terminal for using the configuration information for the srb. in this way, the srb can be established on the secondary node, and used to transmit the rrc message between the secondary node and the terminal, thus improving efficiency in the management of radio resources on the secondary node.
    公开号:BR112019019652A2
    申请号:R112019019652
    申请日:2018-03-20
    公开日:2020-04-22
    发明作者:Liu Jing；Dai Mingzeng；Peng Wenjie；Guo Yi
    申请人:Huawei Tech Co Ltd；
    IPC主号:
    专利说明:

    CONFIGURATION METHOD AND APPLIANCE, RRC MESSAGE TRANSMISSION METHOD AND APPLIANCE, LEGIBLE STORAGE MEDIA
    BY COMPUTER, AND SYSTEM [001] This application claims priority to Chinese Patent Application No. 201710179753.7, filed at the Chinese Patent Office on March 23, 2017 and entitled METHOD AND CONFIGURATION APPARATUS, AND SYSTEM, which is incorporated here by reference in your totality.
    TECHNICAL FIELD [002] This request relates to the field of communication technologies, and in particular, to a method and apparatus of configuration, and a system.
    BACKGROUND [003] In a wireless communications system, considering limited bandwidth resources and coverage of a single cell or base station (or referred to as a node), a service can be provided to a terminal using radio resources from more than than a cell or base station, to better meet capacity and coverage requirements.
    [004] When a service is provided to a terminal using radio resources from more than one base station, it is possible that a transmission latency between base stations cannot satisfy a scaling requirement. Therefore, a dual connectivity technology (Dual Connectivity, DC) is proposed, and has relatively good application in a non-ideal backhaul scenario between a master base station and a secondary base station.
    [005] In a current dual connectivity system, a signaling radio bearer (SRB) carrier is provided by a master base station, a
    Petition 870190111972, of 11/01/2019, p. 7/100
    2/85 secondary base does not provide an SRB and all radio resource control (RRC) messages from a terminal are processed by the master base station. This is not beneficial for improving the efficiency of RRC message processing.
    SUMMARY [006] Modalities of this request provide a method and apparatus for configuration, and a system, with the expectation of establishing a SRB on a secondary node, to implement direct RRC message transmission between the secondary node and a terminal. This is beneficial for improving the efficiency of RRC message processing.
    [007] According to one aspect, a configuration method, applied to a communications system, is provided. The communications system includes a master node and a secondary node that jointly provide a service for a terminal. The method includes: generating, by the secondary node, configuration information for a signaling radio carrier (SRB), and sending the configuration information to the SRB to the master node, so that the configuration information to the SRB is sent to the terminal through the master node; and receive, by the secondary node, a result of configuring the SRB through the terminal by using the configuration information for the SRB, where the SRB is used to transmit a radio resource control (RRC) message between the secondary node and the terminal .
    [008] According to another aspect, a configuration method, applied to a communications system, is provided. The communications system includes a master node and a secondary node that together provide a service for a
    Petition 870190111972, of 11/01/2019, p. 8/100
    3/85 terminal. The method includes: receiving, through the terminal, configuration information for a SRB of the secondary node from the master node, configuring the SRB by using the configuration information for the SRB and sending a result of configuring the SRB, where the SRB is used to transmit an RRC message between the secondary node and the terminal.
    [009] In accordance with yet another aspect, a configuration method is provided, applied to a communications system. The communications system includes a master node and a secondary node that jointly provide a service for a terminal. The method includes: receiving, by the master node, configuration information from an SRB of the secondary node, and sending the configuration information to the SRB to the terminal; and receive, by the master node, a result of configuring the SRB through the terminal for using the configuration information for the SRB, and sending the configuration result to the secondary node, where the SRB is used to transmit an RRC message between the secondary node and the terminal.
    [0010] In the previous aspects, the configuration information for the SRB can also be referred to as SRB configuration information or direct secondary node RRC configuration information (direct S-RRC). The configuration information for the SRB (the SRB configuration information or the direct S-RRC configuration information) is used to configure the SRB to directly transmit the RRC message between the secondary node and the terminal. That is, the configuration information for the SRB (the SRB configuration information or the direct S-RRC configuration information) is used by the terminal to configure the SRB based on the configuration information, so that the RRC message is transmitted
    Petition 870190111972, of 11/01/2019, p. 9/100
    4/85 directly between the terminal and the secondary node. In addition, the configuration result can also be referred to as a result of direct S-RRC configuration or a result of secondary node RRC configuration.
    [0011] It can be learned that in the previous aspects, the configuration information for the SRB that is used to transmit the RRC message between the secondary node and the terminal can be sent to the terminal through the master node, and after the terminal configures the SRB the secondary node, the terminal sends the configuration result to the secondary node directly or through the master node. In this way, the RRC message can be transmitted directly between the secondary node and the terminal, and this is beneficial for improving the efficiency of RRC message processing.
    [0012] In an implementation, the terminal sends the configuration result directly to the secondary node, that is, the terminal sends the configuration result to the secondary node for using the configured SRB; or the terminal sends the configuration result to the master node, so that the configuration result is sent to the secondary node through the master node.
    [0013] In an implementation, the master node sends the first indication information to the secondary node, where the first indication information is used to instruct the secondary node to establish the SRB or is used to instruct the secondary node to generate the information configuration for the SRB. The secondary node receives the first indication information, and generates the configuration information for the SRB based on the first indication information. In this way, the secondary node can establish the SRB based on a
    Petition 870190111972, of 11/01/2019, p. 10/100
    5/85 master node instruction, and this helps the master node to control the secondary node's SRB establishment based on a requirement, making it more flexible to control the secondary node's SRB establishment.
    [0014] Optionally, the first indication information can be carried in an add request message sent by the master node to the secondary node, where the add request message is used to request the addition of a secondary node. Alternatively, the first indication information can be carried in a modification request message sent by the master node to the secondary node, where the modification request message is used to request the modification of a configuration of a secondary node.
    [0015] In an implementation, the master node sends an add request message to the secondary node, where the add request message is used to request the addition of a secondary node. When the secondary node receives the add request message from the master node, the secondary node generates configuration information for the SRB. In this way, information elements transmitted between the master node and the secondary node can be reduced. When the secondary node is added, the SRB is established on the secondary node by default.
    [0016] In an implementation, the configuration information for the SRB can be a RRC protocol data unit (PDU), or it can be part of an RRC PDU.
    [0017] In an implementation, configuration information for the SRB can be sent to the master node after the secondary node performs security processing. In this case,
    Petition 870190111972, of 11/01/2019, p. 11/100
    6/85 before the secondary node sends the configuration information to the SRB to the master node, the secondary node performs security processing on the configuration information to the SRB, where the security processing includes integrity protection and / or encryption . Likewise, after the terminal receives the configuration information for the SRB, the terminal performs security processing on the configuration information for the SRB and then configures the SRB of the secondary node by using the configuration information for the SRB, where security processing includes integrity checking and / or decryption.
    [0018] In an implementation, the configuration information for the SRB includes at least one of the following information: an SRB identifier, an SRB radio link control layer (RLC) configuration, a logical channel configuration, and an SRB security parameter. The SRB security parameter includes, for example, information about a security algorithm and / or a parameter used to derive a security key. The security algorithm includes, for example, an encryption and / or integrity protection algorithm. The information about the security algorithm can be information used to indicate the security algorithm, for example, it can be an indication or an algorithm identifier, or it can be the security algorithm.
    [0019] In an implementation, the secondary node can add the configuration information for the SRB to an acknowledgment message sent to the master node. The acknowledgment message is a reply message (that is, an addition request acknowledgment message) to the
    Petition 870190111972, of 11/01/2019, p. 12/100
    7/85 add request message used to request the addition of a secondary node or a reply message (that is, a change request acknowledgment message) to the change request message used to request the modification of a configuration secondary node. In other words, the previous method also includes: receiving, by the secondary node, an addition request message or a modification request message from the master node; and the sending, by the secondary node, of the configuration information to the SRB to the master node includes: sending, by the secondary node, an add request acknowledgment message or a modification request acknowledgment message to the master node, where the add request acknowledgment message or the change request acknowledgment message includes the configuration information for the SRB.
    [0020] It can be learned that the configuration information for the SRB can be sent by the secondary node to the master node in a secondary node addition process (an initial dual connectivity configuration process) or a secondary node modification process , so that signaling can be saved, and communication efficiency can be improved. When configuration information for the SRB is sent by the secondary node to the master node in the secondary node modification process, the secondary node modification process can be triggered by the master node, or it can be triggered by the secondary node. When the secondary node modification process is triggered by the secondary node, the previous method also includes: sending, through the secondary node, a required modification message to the master node, where
    Petition 870190111972, of 11/01/2019, p. 13/100
    8/85 the required modification message is used to request that the master node allow the RRC message to be transmitted or the SRB to be established between the secondary node and the terminal.
    [0021] In an implementation, the master node can send the configuration information to the secondary node's SRB to the terminal using a RRC connection reconfiguration message from the master node. Correspondingly, the terminal can send the result of configuring the SRB to the master node using a complete RRC connection reconfiguration message. That is, the sending, by the master node, of the configuration information to the SRB of the secondary node to the terminal includes: sending, by the master node, an RRC connection reconfiguration message to the terminal, where the RRC connection reconfiguration message carries the configuration information to the SRB of the secondary node, and the reception, by the master node, of a result of configuring the SRB by the terminal includes: receiving, by the master node, a complete RRC connection reconfiguration message from the terminal, where the Complete RRC connection reconfiguration message carries the configuration result. Correspondingly, the receipt by the terminal of configuration information for a SRB of the secondary node from the master node includes: receiving, by the terminal, the RRC connection reconfiguration message from the master node, where the connection reconfiguration message RRC transports the configuration information to the secondary node's SRB, and sending a configuration result to the master node via the terminal includes: sending, through the terminal, the complete RRC connection reconfiguration message to the
    Petition 870190111972, of 11/01/2019, p. 14/100
    9/85 master node, where the complete RRC connection reconfiguration message carries the configuration result.
    [0022] In an implementation, when the terminal sends the configuration result to the secondary node through the master node, the terminal sends second indication information to the master node, to indicate a result of configuring the SRB of the secondary node through the terminal. In this way, even when the master node cannot analyze the configuration result, the master node can learn from the result of configuring the SRB of the secondary node through the terminal.
    [0023] In an implementation, the master node can send the configuration information to the SRB of the secondary node to the terminal using a RRC connection reconfiguration message from the master node. A complete RRC reconfiguration message sent by the terminal is a result of configuration. In this case, when the master node receives the complete RRC connection reconfiguration message, the configuration is considered to be successful. The complete RRC connection reconfiguration message can be a complete RRC connection reconfiguration message sent to the master node, or it can be a complete RRC connection reconfiguration message sent to the secondary node.
    [0024] In an implementation, when the terminal sends the configuration result to the secondary node through the master node, the master node sends the configuration result using a complete secondary node reconfiguration message. Optionally, the master node sends a complete secondary node reconfiguration message to the secondary node, where the complete secondary node reconfiguration message carries the configuration result. Optionally, the node
    Petition 870190111972, of 11/01/2019, p. 15/100
    10/85 master sends a complete secondary node reconfiguration message to the secondary node, where the complete secondary node reconfiguration message is the result of configuration. In that case, when the secondary node receives the complete secondary node reconfiguration message, the configuration is considered to be successful.
    [0025] In an implementation, the master node can analyze the configuration result and, when the configuration result is successful, send data from the terminal to the secondary node or request a core network to send data from the terminal to the node secondary. Alternatively, the master node can determine, based on the second indication information, the result of configuring the SRB of the secondary node via the terminal and, when the configuration result is successful, send data from the terminal to the secondary node or request a core network to send data from the terminal to the secondary node.
    [0026] In an implementation, the master node sends security information used for the SRB of the secondary node to the secondary node, where the security information used for the SRB of the secondary node is also referred to as security information for direct S-RRC . The security information includes at least one of the following information: a security key and information about a security algorithm. The security algorithm includes an encryption algorithm and / or an integrity protection algorithm. The information about the security algorithm can be information used to indicate the security algorithm, for example, it can be an indication or an algorithm identifier, or it can be the security algorithm. The secondary node receives the information
    Petition 870190111972, of 11/01/2019, p. 16/100
    11/85 security, and performs security processing for the SRB based on the security information. The master node can send security information to the secondary node before the secondary node generates the configuration information for the SRB, that is, before the master node receives the configuration information for the SRB of the secondary node. After the secondary node generates the configuration information for the SRB, the secondary node can perform security processing on the configuration information for the SRB by using the security information. The safety information can be carried in the add request message or in the change request message.
    [0027] In an implementation, the master node sends a group of keys (also referred to as a list of keys) to the secondary node, where the group of keys includes a plurality of keys, so that the secondary node selects a key from key group when updating a key. The secondary node receives the key group from the master node, and selects a key from the key group when updating the key. In this way, the secondary node can update the key on its own, thus further improving the configuration efficiency on the secondary node.
    [0028] Optionally, the master node can send the group of keys based on a requirement of the secondary node. To be specific, the secondary node sends the third indication information to the master node used to instruct the master node to send the group of keys.
    [0029] Optionally, the master node can send a group of count values (COUNT), that is, a group of count values, used to derive the keys in the group of keys
    Petition 870190111972, of 11/01/2019, p. 17/100
    12/85 for the secondary node. The secondary node receives the group of count values, and sends a count value used to derive the selected key to the terminal when updating a key, so that the terminal also completes the synchronous key update.
    [0030] Optionally, the master node can send a group of count values, that is, a group of count values, used to derive the keys in the group of keys to the terminal. When the secondary node updates a key, the secondary node sequentially selects a key from the group of keys, and instructs the terminal to update the key, that is, it sends a notification message to the terminal to instruct the terminal to update the key. When the terminal receives the notification message, the terminal sequentially selects a count value from the group of count values, to perform synchronous key update.
    [0031] Optionally, the master node sends, to the secondary node, association information between a key in the key group and a count value used to derive the key in the key group. When the secondary node updates a key, the secondary node sends association information between a selected key and a count value used to derive the key to the terminal. The terminal receives the association information, selects the count value based on the association information, and performs the synchronous key update based on the count value.
    [0032] In an implementation, after configuring the SRB of the secondary node, the secondary node can directly send an RRC reconfiguration message to the terminal
    Petition 870190111972, of 11/01/2019, p. 18/100
    13/85 for configuration. The terminal receives the RRC connection reconfiguration message, and when reconfiguration corresponding to the RRC connection reconfiguration message fails, it re-stores configuration before the RRC connection reconfiguration message is received. Optionally, the terminal can also send a notification message to the secondary node (directly or through the master node), to notify the secondary node that the RRC connection reconfiguration fails.
    [0033] In an implementation, the configuration information for the secondary node's SRB further includes uplink RRC configuration information, where the uplink RRC configuration information is used to configure a way in which the terminal sends a uplink RRC message to the secondary node.
    [0034] In accordance with yet another aspect, this request provides a configuration device, including units or means (means) configured to carry out the steps in any implementation of any of the previous aspects.
    [0035] In yet another aspect, this application provides a configuration apparatus, including at least one processing element and at least one storage element, where the at least one storage element is configured to store a program and data, and the at least one processing element is configured to execute the method provided in any implementation of any of the foregoing aspects.
    [0036] In accordance with yet another aspect, this application provides a computer program, where, when executed by a processor, the program is used to execute the
    Petition 870190111972, of 11/01/2019, p. 19/100
    14/85 method in any implementation of any of the above.
    [0037] In accordance with yet another aspect, a computer-readable storage medium is provided, including the previous program.
    [0038] According to yet another aspect, a communications system is provided, including any of the previous configuration devices.
    [0039] In addition, the modalities of this request also provide a method and apparatus for transmitting RRC messages, and a system, in the hope of further improving the reliability of the transmission of uplink RRC messages when an SRB can be established in a secondary node. In addition, the RRC message transmission method and apparatus, and the system can be combined with the previous configuration method and apparatus, and the previous system.
    [0040] According to one aspect, an RRC message transmission method, applied to a communications system, is provided. The communications system includes a master node and a secondary node that jointly provide a service for a terminal. The method includes: receiving, by the terminal, a downlink RRC message from the secondary node, where the downlink RRC message is received by the master node from the secondary node and sent to the terminal, or the downlink RRC message is sent by the secondary node to the terminal; and sending, through the terminal, an uplink RRC message, where the uplink RRC message is a response message to the uplink RRC message, and a path in which the terminal
    Petition 870190111972, of 11/01/2019, p. 20/100
    15/85 sends the uplink RRC message is the same path that the terminal receives the uplink RRC message. To be specific, when the downlink RRC message is received by the master node from the secondary node and sent to the terminal, the uplink RRC message is sent by the terminal to the master node, and then sent by the master node to the secondary node. Alternatively, when the downlink RRC message is sent by the secondary node to the terminal, the uplink RRC message is sent by the terminal to the secondary node. 0 sent here means to be sent directly without being forwarded by the master node.
    [0041] According to another aspect, an RRC message transmission method is provided, applied to a communications system. The communications system includes a master node and a secondary node that jointly provide a service for a terminal. The method includes: obtaining or generating, by the master node, uplink RRC configuration information from the secondary node, where the uplink RRC configuration information is used to configure a way in which the terminal sends a link RRC message ascending to the secondary node; and sending, through the master node, the uplink RRC configuration information to the terminal, so that the terminal sends uplink RRC messages based on the uplink RRC configuration information. The master node can obtain the uplink RRC configuration information from the secondary node.
    [0042] In accordance with yet another aspect, an RRC message transmission method is provided, applied to a
    Petition 870190111972, of 11/01/2019, p. 21/100
    16/85 communications system. The communications system includes a master node and a secondary node that jointly provide a service for a terminal. The method includes: receiving, by the terminal, uplink RRC configuration information from the secondary node from the master node, where uplink RRC configuration information is used to configure a way in which the terminal sends an RRC message uplink to the secondary node; and sending, through the terminal, the uplink RRC message to the secondary node based on the uplink RRC configuration information.
    [0043] In an implementation, the way of sending the uplink RRC message includes: sending, through the terminal, the uplink RRC message to the secondary node to the secondary node; or send, through the terminal, the uplink RRC message to the secondary node to the secondary node through the master node; or send, through the terminal, the uplink RRC message to the secondary node to the secondary node, where the uplink RRC message is a response message to a downlink RRC message from the secondary node; or send, through the terminal, the uplink RRC message to the secondary node to the secondary node through the master node, where the uplink RRC message is a response message to a downlink RRC message from the secondary node; or send, through the terminal based on a measurement result of a cell of the secondary node, the uplink RRC message for the secondary node to the secondary node directly or through the master node; or send, through the terminal, the link RRC message
    Petition 870190111972, of 11/01/2019, p. 22/100
    17/85 upstream to the secondary node in the same path as a downlink RRC message from the secondary node.
    [0044] Optionally, when the RRC message transmission method is combined with the previous configuration method, the previous configuration information for the SRB can include the uplink RRC configuration information or the configuration information for the SRB and uplink RRC configuration information can be sent to the terminal using a master node RRC connection reconfiguration message.
    [0045] Optionally, when the terminal sends, based on the measurement result of the secondary node cell, the uplink RRC message to the secondary node to the secondary node directly or through the master node, the RRC configuration information of forward uplink may include a threshold. When a measurement value obtained by the terminal by measuring the secondary node's cell is greater than the threshold, the terminal sends the uplink RRC message to the secondary node to the secondary node. When a measurement value obtained by the terminal for measuring the cell of the secondary node is less than the threshold, the terminal sends the uplink RRC message to the secondary node to the secondary node through the master node. When a measurement value obtained by the terminal for measuring the secondary node cell is equal to the threshold, the terminal can send the uplink RRC message to the secondary node to the secondary node directly or through the master node.
    [0046] In accordance with yet another aspect, this request provides an RRC message transmission device, including units or means (means) configured to carry out the steps
    Petition 870190111972, of 11/01/2019, p. 23/100
    18/85 in any implementation of any of the above.
    [0047] In yet another aspect, this application provides an RRC message transmission apparatus, including at least one processing element and at least one storage element, where at least one storage element is configured to store a program and data, and at least one processing element is configured to execute the method provided in any implementation of any of the foregoing aspects.
    [0048] In accordance with yet another aspect, this application provides a computer program, where when executed by a processor, the program is used to execute the method of any implementation of any of the previous aspects.
    [0049] In accordance with yet another aspect, a computer-readable storage medium is provided, including the previous program.
    [0050] In accordance with yet another aspect, a communications system is provided, including any of the previous configuration devices.
    [0051] It can be learned that in the previous aspects, the uplink RRC message to the secondary node can be transmitted in a way configured by the master node or it can be transmitted in the same path as the downlink RRC message. In this way, the lack of reliability generated by a plurality of uplink RRC message transmission possibilities is alleviated.
    [0052] Furthermore, the modalities of this application also provide a method and apparatus for configuration, and a system, in
    Petition 870190111972, of 11/01/2019, p. 24/100
    19/85 expectation to further improve the efficiency of mobility management when an SRB can be established on a secondary node. In addition, the configuration method and apparatus, and the system can be combined with the previous configuration method and apparatus, and the previous system.
    [0053] According to one aspect, a configuration method, applied to a communications system, is provided. The communications system includes a master node (MN) and a secondary node (SN) that jointly provide a service for a terminal. The method includes the following steps:
    receiving, by the secondary node, measurement configuration information from the master node, where the measurement configuration information is used to configure a condition to trigger the secondary node to send a measurement result to the master node;
    receiving, by the secondary node from the terminal, a measurement report obtained by the terminal for measuring a cell of the secondary node; and when the measurement report includes a measurement result satisfying the previous condition, send the measurement result to the master node via the secondary node.
    [0054] According to another aspect, a configuration method is provided, applied to a communications system, where the communications system includes an MN and an SN that together provide a service for a terminal, and the method includes the following steps :
    send, by the master node, measurement configuration information to the secondary node, where the measurement configuration information is used to configure a
    Petition 870190111972, of 11/01/2019, p. 25/100
    20/85 condition to trigger the secondary node to send a measurement result to the master node; and receiving, by the master node, a measurement result satisfying the previous condition of the secondary node, where the measurement result is obtained by the terminal by measuring a cell of the secondary node and reported to the secondary node.
    [0055] In an implementation, the measurement configuration information includes a threshold, and the previous condition is that the measurement result is greater than or equal to the threshold. To be specific, the master node sends the threshold to the secondary node, the secondary node receives the threshold and, when the measurement result is greater than or equal to the threshold, the secondary node sends the measurement result to the master node.
    [0056] In an implementation, the previous method also includes: configuring, through the secondary node, the threshold for the terminal. In this way, a measurement report reported by the terminal is a measurement report satisfying the threshold requirement, and the secondary node can directly send a measurement result in the measurement report to the master node, without determining whether the measurement result meets the requirement. threshold.
    [0057] In an implementation, the information sent by the secondary node to the master node also includes a cell or beam identifier, that is, a cell or beam identifier corresponding to the measurement result satisfying the condition. That is, the previous method also includes: sending, by the secondary node, a cell or beam identifier corresponding to the measurement result to the master node.
    [0058] In accordance with yet another aspect, this application provides a configuration device, including units or
    Petition 870190111972, of 11/01/2019, p. 26/100
    21/85 means (means) configured to carry out the steps in any implementation of any of the previous aspects.
    [0059] In accordance with yet another aspect, this application provides a configuration apparatus, including at least one processing element and at least one storage element, where at least one storage element is configured to store a program and data, and the at least one processing element is configured to execute the method provided in any implementation of any of the previous aspects.
    [0060] In accordance with yet another aspect, this application provides a computer program, where, when executed by a processor, the program is used to execute the method in any implementation of any of the previous aspects.
    [0061] In accordance with yet another aspect, a computer-readable storage medium is provided, including the previous program.
    [0062] In accordance with yet another aspect, a communications system is provided, including any of the previous configuration devices.
    [0063] It can be learned that, in the previous aspects, the master node can configure the secondary node to report, in a specific condition, the measurement result of the secondary node's cell by the terminal, thus improving the performance of mobility management.
    BRIEF DESCRIPTION OF THE DRAWINGS [0064] Figure 1 is a schematic diagram of a scenario of dual connectivity according to one modality of this request;
    Petition 870190111972, of 11/01/2019, p. 27/100
    22/85
    Figure 2 (a) is a schematic diagram of a dual LTE-NR connectivity scenario according to one embodiment of this request;
    Figure 2 (b) is a schematic diagram of another scenario of dual LTE-NR connectivity according to one modality of this request;
    Figure 2 (c) is a schematic diagram of yet another LTE-NR dual connectivity scenario according to one modality of this request;
    Figure 3 (a) is a schematic architectural diagram of a wireless protocol for dual connectivity, according to one embodiment of this request;
    Figure 3 (b) is a schematic architectural diagram of another wireless protocol for dual connectivity, according to one embodiment of this request;
    Figure 4 is a schematic diagram of an RRC message according to an embodiment of this request;
    Figure 5 is a schematic diagram of a configuration method according to an embodiment of this application;
    Figure 6 is a schematic diagram of a method of establishing a radio carrier according to one embodiment of this application;
    Figure 7 is a schematic diagram of a method of configuration according to one embodiment of this application;
    Figure 8 is a schematic diagram of a COUNT parameter according to an embodiment of this request;
    Figure 9 is a schematic diagram of an RRC transmission method according to an embodiment of this application;
    Figure 10 is a schematic diagram of another method of transmitting RRC according to an embodiment of this application;
    Petition 870190111972, of 11/01/2019, p. 28/100
    23/85
    Figure 11 is a schematic diagram of a configuration method according to an embodiment of this application;
    Figure 12 is a schematic diagram of an apparatus applied to an SN according to an embodiment of this application;
    Figure 13 is a schematic diagram of an appliance applied to an MN according to an embodiment of this application;
    Figure 14 is a schematic diagram of an apparatus applied to a terminal according to an embodiment of this application;
    Figure 15 is a schematic structural diagram of a RAN node according to an embodiment of this application; and
    Figure 16 is a schematic structural diagram of a terminal according to an embodiment of this application.
    DESCRIPTION OF THE MODALITIES [0065] The following are some terms of this application:
    (1) A terminal, also referred to as user equipment (User Equipment, UE), is a device that provides voice and / or data connectivity to a user, for example, a portable device or a vehicle device that has a function wireless connection. Currently, some terminals are, for example, a mobile phone, a tablet, a notebook, a palmtop, a mobile Internet device (Mobile Internet Device, MID), and a wearable device such as a smart watch, a smart band and a pedometer .
    (2) A radio access network (Radio Access Network, RAN) is a part of a network that connects a terminal to a wireless network. A RAN node or device is a node or device on the radio access network, and can also be called a
    Petition 870190111972, of 11/01/2019, p. 29/100
    24/85 base station. Currently, some RAN nodes are, for example, a gNB, a transmission / reception point (Transmission Reception Point, TRP), an evolved NodeB (evolved Node B, eNB), a radio network controller (Radio Network Controller, RNC ), a NodeB (NodeB, NB), a base station controller (Base Station Controller, BSC), a base transceiver station (Base Transceiver Station, BTS), a home base station (for example, NodeB or Domestic Node B HNB) , a baseband unit (BaseBand Unit, BBU) or a WiFi access point (Access Point, AP). In addition, in a network structure, the RAN can include a centralized unit node (Centralized Unit, CU) and distributed unit nodes (Distributed Unit, DU). In this structure, protocol layers of an eNB n in Long Term Evolution (Long Term Evolution, LTE) are divided, where functions of some protocol layers are divided for CU for centralized control, and functions of part or all of the layers Remaining protocol points are divided for DUs, which are controlled by CU in a centralized manner.
    (3) The term plurality of means two or more than two, and other quantifiers are similar. The term and / or describes an association relationship to describe associated objects and represents that three relationships can exist. For example, A and / or B can represent the following three cases: Only A exists, A and B exist and only B exists. The character / usually indicates a relationship or between the associated objects.
    [0066] With reference to Figure 1, Figure 1 is a schematic diagram of a scenario of dual connectivity according to one modality of this request. As shown in Figure 1,
    Petition 870190111972, of 11/01/2019, p. 30/100
    25/85 a RAN 110 node and a RAN 120 node jointly provide a service for a terminal 130. The RAN 110 node is a master node (Master Node, MN). The RAN 120 node is a secondary node (Secundary node, SN). There is a control plane connection and a user plane connection between the MN 110 and a core network (Core Network, CN) 140. A user plane connection may or may not exist between the SN 120 and the core network 140. Sl-U represents a user plane connection and Sl-C represents a control plane connection. When a user plan connection does not exist between SN 120 and core network 140, data for terminal 130 can be transferred from MN 110 to SN 120 in a Packet Data Convergence Protocol layer Convergence Protocol, PDCP). The MN and SN are also referred to as the master base station and the secondary base station.
    [0067] Dual connectivity can be implemented between intra-RAT RAN nodes, or it can be implemented between inter-RAT RAN nodes. For example, with the evolution of wireless communication technologies, dual connectivity can be implemented in a scenario of joint LTE networks (also referred to as 4G) and Novo Rádio (New Radio, NR) (also referred to as 5G), and such dual connectivity is known as dual LTE-NR connectivity. In this way, a terminal can obtain radio resources from both LTE and NR air interfaces for data transmission, thereby obtaining a gain in transmission speed. Dual LTE-NR connectivity mainly includes the following three architectures, described separately below with reference to Figure 2 (a), Figure 2 (b) and Figure 2 (c), where an interface between a core network and a RAN node is represented by Sl,
    Petition 870190111972, of 11/01/2019, p. 31/100
    26/85 an interface between RAN nodes is represented by X2 (which can also be called the Xn interface). Such a form of representation is merely an example and is not intended to limit this request.
    [0068] With reference to Figure 2 (a), Figure 2 (a) is a schematic diagram of a dual LTE-NR connectivity scenario according to one modality of this request. As shown in Figure 2 (a), an LTE eNB serves as an MN, and control plane and user plane connections can be established for a terminal between the MN and an evolved Packet Core, EPC of an LTE system. A NR gNB serves as an SN, and a user piano connection can be established between the SN and the EPC. It can be learned that in the scenario shown in Figure 2 (a), LTE eNB is used as an anchor and LTE eNB connects to the LTE core network.
    [0069] With reference to Figure 2 (b), Figure 2 (b) is a schematic diagram of another scenario of dual LTE-NR connectivity according to one modality of this request. A difference from Figure 2 (a) lies in the fact that an NR gNB is used as an anchor and the NR gNB connects to an NR core network, which can be called the next generation core (Next Generation Core, NGC) or a 5G core network (5th Generation Core Network, 5G-CN). That is, the NR gNB serves as an MN, and connections from the control plane and user plane can be established to a terminal between the MN and the NGC. An eNB LTE serves as an SN, and a user plane connection can be established between the SN and the NGC.
    [0070] With reference to Figure 2 (c), Figure 2 (c) is a schematic diagram of yet another scenario of
    Petition 870190111972, of 11/01/2019, p. 32/100
    27/85 dual LTE-NR connectivity according to one modality of this request. As in Figure 2 (a), an LTE eNB is used as an anchor and a difference from Figure 2 (a) lies in the fact that LTE eNB connects to an NR NGC core network. That is, the LTE eNB serves as an MN and the control plane and user plane connections can be established to a terminal between the MN and the NGC. A gNB NR serves as an SN, and a user plane connection can be established between the SN and the NGC.
    [0071] In the three previous scenarios, the user plan connection may not be established between the SN and the core network, and the data is transferred through the MN. For example, in a downlink direction, data for a terminal reaches the first MN, and the MN transfers the data to the terminal with SN in a PDCP layer. One form of the downloaded data is, for example, a protocol data unit PDCP (Protocol Data Unit, PDU).
    [0072] In dual connectivity, a data radio bearer (Data Radio Bearer, DRB) can be provided only by MN or SN, or can be provided by MN and SN. When DRB is provided only by MN, DRB is referred to as a carrier of master cell groups (Master Cell Group, MCG). When DRB is provided only by SN, DRB is referred to as a secondary cell group carrier (Secondary Cell Group, SCG). When DRB is provided by MN and SN, DRB is referred to as a split bearer.
    [0073] Descriptions are provided below with reference to Figure 3 (a) and Figure 3 (b) Figure 3 (a) and Figure 3 (b) are schematic architectural diagrams of
    Petition 870190111972, of 11/01/2019, p. 33/100
    28/85 wireless protocols of dual connectivity according to one modality of this request. As shown in Figure 3 (a) and Figure 3 (b), when a carrier is provided only by an MN, that is, a data stream flows from a core network only to the MN, the carrier is an MCG carrier (bearer). When a carrier is provided only by an SN, that is, a data stream flows from a core network only to the SN, the carrier is an SCG carrier. When a carrier is provided by both an MN and an SN, that is, a data stream is discharged into the MN or SN, the carrier is a split bearer. For differentiation, a carrier division in the MN can be referred to as a split carrier of MCG (shown in Figure 3 (a)), and a carrier division in the SN can be referred to as a split carrier of SCG (shown in Figure 3 ( B)).
    [0074] In a current dual LTE connectivity system, a signaling radio bearer (SRB) carrier is provided by an MN, and an SN does not provide an SRB. The SRB is established only between a terminal and the MN for the transmission of a radio resource control message (Radio Resource Control, RRC), and all SN RRC messages are sent to the terminal via the MN. However, with the evolution of technologies, it is expected that SN will be able to provide an SRB independently, so that the rapid RRC configuration can be implemented. Therefore, an RRC message can be transmitted not only between the MN and the terminal, but also between the SN and the terminal. In that case, there can be three types of RRC messages.
    [0075] With reference to Figure 4, Figure 4 is a schematic diagram of an RRC message according to a modality
    Petition 870190111972, of 11/01/2019, p. 34/100
    29/85 of this order. As shown in Figure 4, when an SN can provide an SRB, there are three types of RRC messages: a master RRC message (M-RRC), a direct RRC secondary node message (direct S-RRC) and a node RRC message embedded secondary (embedded S-RRC). The M-RRC message is used for an MN, and is transmitted directly between the MN and a terminal, that is, it is terminated directly between the MN and the terminal. The direct S-RRC message is used for the SN, and is transmitted directly between the SN and the terminal. The embedded S-RRC message is used for the SN, and the embedded S-RRC message is encapsulated in the M-RRC message, and can be used as an RRC container (container). The RRC container is an RRC PDU satisfying an SN protocol requirement. It can be learned that two types of RRC messages, that is, the embedded S-RRC message and the direct S-RRC message, can be used for SN.
    [0076] However, currently, there is no method available to establish a SRB in an SN. In addition, an RRC message between a terminal and an SN can be transferred using an SRB in an MN, or it can be transferred directly using an SRB in an SN, but currently there is also no method available to select a way to transfer the RRC message between an the terminal and the SN.
    [0077] In view of this, the following modality provides a method of configuration, to establish an SRB in an SN, so that an RRC message can be transmitted directly between a terminal and the SN.
    [0078] With reference to Figure 5, Figure 5 is a schematic diagram of a configuration method according to one embodiment of this application. As shown in Figure 5, the method
    Petition 870190111972, of 11/01/2019, p. 35/100
    30/85 includes the following steps.
    S510: An SN generates configuration information for an SRB, where the SRB is used to transmit an RRC message between the SN and a terminal. That is, the RRC message can be transmitted directly by the SN to the terminal using the SRB, without being forwarded by an MN, or the RRC message can be transmitted directly by the terminal to the SN using the SRB, without being forwarded by an MN. The configuration information for the SRB can also be referred to as configuration information for the SRB or direct SRRC configuration information. A configuration information name for the SRB is not limited in this order. The configuration information for the SRB (the configuration information for the SRB or the configuration information for direct S-RRC) is used to configure the SRB to directly transmit the RRC message between the terminal and the SN. That is, the configuration information for the SRB (the configuration information for the SRB or the configuration information for the direct S-RRC) is used by the terminal to configure the SRB based on the configuration information, so that the RRC message be transmitted directly between the terminal and the secondary node.
    S520: The SN sends the configuration information to the SRB for an MN.
    [0079] The MN receives the configuration information for the SN's SRB, and performs the following operation:
    S530: The MN sends the configuration information to the SN's SRB to the terminal.
    [0080] The terminal receives the configuration information for the SN SRB, and performs the following operation:
    S540: The terminal configures the SRB for using the
    Petition 870190111972, of 11/01/2019, p. 36/100
    31/85 configuration information to the SN SRB, and sends a configuration result to the SN. The terminal can send the configuration result to the SN via the MN, or it can directly send the configuration result to the SN. The terminal can then perform steps S550 or S570.
    S550: The terminal sends the result of configuring the SRB to the MN, so that the configuration result can be sent to the SN via the MN.
    [0081] The MN receives the configuration result and performs the following step:
    S560: 0 MN sends the configuration result to SN.
    S570: The terminal sends the configuration result to the SN. That is, the terminal directly sends the result of configuring the SRB from SN to SN using the configured SRB.
    [0082] In this way, a configuration for the SRB by SN can be sent to the terminal via the MN and, after the terminal has configured the SRB, the terminal sends the configuration result to the SN directly or via the MN. In this way, an RRC message can be transmitted directly between the SN and the terminal, and this is beneficial for improving the efficiency of RRC message processing.
    [0083] In step S510, the SN can generate the configuration information for the SRB based on an instruction from the MN, or it can generate the configuration information for the SRB by default when learning that the MN requests to add the SN as an SN . That is, before step S510, the previous method can also include step S501 or step S502:
    S501: 0 MN sends the first indication information to the SN, where the first indication information is used to instruct the SN to establish a SRB or is used to
    Petition 870190111972, of 11/01/2019, p. 37/100
    32/85 instruct SN to generate configuration information for an SRB. The SN receives the first indication information, and generates the configuration information for the SRB based on the first indication information. When the first indication information is used to instruct the SN to establish the SRB, the SN generates the configuration information for the SRB, and sends the configuration information to the SRB to the terminal via the MN, to complete the configuration of the SRB and complete the establishment of the SRB. When the first indication information is used to instruct the SN to generate the configuration information for the SRB, it indicates that the SRB must be established in the SN; therefore, the SN generates the configuration information for the SRB and sends the configuration information to the SRB to the terminal via the MN, to complete the configuration of the SRB and complete the establishment of the SRB. In this way, the secondary node can establish the SRB based on an instruction from the master node, and this helps the master node to control the establishment of the SRB of the secondary node based on a requirement, making it more flexible to control the establishment of the SRB of the node secondary.
    S502: 0 SN receives a request message from the MN, where the request message is used to request the addition of the SN as an SN. The SN receives the request message, learns that the SN must be added as SN and, when the SN is added as SN, establishes an SRB by default, that is, it generates configuration information for the SRB by default. That is, when the SN discovers that the SN is required to be added as an SN, the SN can generate configuration information for the SRB, without being instructed, by the MN using an information element, to produce the information of
    Petition 870190111972, of 11/01/2019, p. 38/100
    33/85 configuration for the SRB. In this way, information elements transmitted between the MN and the SN can be reduced. When an SN is added, an SRB is established in the SN by default.
    [0084] Optionally, the first indication information in step S501 can be carried in an addition request message sent by the MN to the SN, where the add request message is used to request the addition of an SN. Alternatively, the first indication information can be carried in a modification request message sent by the MN to the SN, where the modification request message is used to request the modification of a configuration of a secondary node. This is further described in a subsequent embodiment, and the details are not described here.
    [0085] In addition, in step S510, the configuration information for the SRB that is generated by the SN can be a protocol data unit RRC (Protocol Data Unit, PDU) or a part of the RRC PDU. For example, if the MN is a RAN node in an LTE system, and the SN is a RAN node in an NR system, the SN generates an NR RRC PDU, where the NR RRC PDU includes at least the configuration information for the SRB of SN. The NR RRC PDU can be a NR RRC connection reconfiguration message (RRC Connection Reconfiguration message). In addition, security processing can be performed in the configuration information for the SRB. For example, SN performs integrity protection and / or encryption processing of configuration information to the SRB, and then sends the configuration information to the SRB to the MN. The MN sends the configuration information to the SRB to the terminal. After the terminal receives the
    Petition 870190111972, of 11/01/2019, p. 39/100
    34/85 configuration for the SRB, it performs integrity check and / or decryption in the configuration information for the SRB.
    [0086] The configuration information for the SRB can include at least one of the following information: an SRB identifier, a radio link control layer configuration (Radio Link Control, RLC) from the SRB, a logical channel configuration, and an SRB security parameter. The SRB security parameter can include, for example, at least one of the following parameters: information about a security algorithm and a parameter used to derive a security key. The security algorithm includes, for example, an encryption and / or integrity protection algorithm. The information about the security algorithm can be information used to indicate the security algorithm, for example, it can be an indication or an algorithm identifier, or it can be the security algorithm. Alternatively, the SN may not send the SRB security parameter, and the terminal and the SN pre-configure the security parameters that keep it consistent. In an optional way, SN and MN use the same security parameter, for example, the same encryption algorithm and / or integrity protection. Alternatively, the security parameter is sent by the MN to the terminal, and does not need to be carried in the configuration information to the SRB. In addition, content carried in the security parameter can be partially carried in the configuration information to the SRB, and partially pre-configured or sent by the MN to the terminal.
    [0087] In step S520, SN can add information
    Petition 870190111972, of 11/01/2019, p. 40/100
    35/85 configuration for the SN SRB to an acknowledgment message sent by the SN to the MN, where the acknowledgment message is a reply message to the add request message used to request the addition of an SN or a reply to the modification request message used to request modification of an SN configuration. In addition, in step S530, the MN can send the configuration information to the SN's SRB to the terminal using an MN RRC connection reconfiguration message.
    [0088] The configuration information for the SN SRB can be sent to the MN as an RRC container (container). The container is, for example, an RRC PDU. In addition, the container can be transported in a message sent by the SN to the MN. After the MN analyzes the container from the message, the MN forwards the container directly to the terminal without analyzing the container. For example, the container is transported in an acknowledgment message sent by the SN to the MN, where the acknowledgment message is a reply message to the request message used to request the addition of an SN or a reply message to the message of modification request used to request to modify an SN configuration.
    [0089] In step S540, the terminal generates a corresponding RRC entity and a Layer 2 entity (for example, an RLC entity) based on the configuration information for the SRB, and activates security processing for direct RRC transmission between the terminal and the SN, to transmit an RRC message from the SN. The entities here are logical entities, and used to implement RRC and layer 2 functions.
    Petition 870190111972, of 11/01/2019, p. 41/100
    36/85 the configuration information for the SRB is carried in the MN RRC connection reconfiguration message, after the terminal receives the MN RRC connection reconfiguration message, the terminal extracts the configuration information for the SRB from the MN message reconfiguration of RRC connection, and analyzes the configuration information for the SRB by using an RRC format from SN. If security processing, for example, integrity protection and / or encryption, is performed on the configuration information for SRB by SN, the terminal can perform security processing, for example, integrity check and / or decryption of information configuration for the SRB using the security parameter.
    [0090] In step S550, the terminal can add the configuration result for a complete RRC connection reconfiguration message, and send the complete RRC connection reconfiguration message to the MN. The configuration result can also be referred to as a result of direct S-RRC configuration or a result of SN RRC configuration. For example, the configuration result can be successful or failed, to indicate that the result of configuring the SN SRB through the terminal is successful or failed. For the configuration result, the terminal can send second indication information to the MN, where the second indication information is used to indicate the configuration result, so that when the MN cannot analyze the configuration result, the MN can learn , based on the second indication information, the result of configuring the SN SRB by the terminal. The second indication information and the configuration result can be transported in one
    Petition 870190111972, of 11/01/2019, p. 42/100
    37/85 same message sent by the terminal to the MN, for example, carried in the complete RRC connection reconfiguration message sent by the terminal to the MN.
    [0091] In addition, the configuration result can be the complete RRC connection reconfiguration message. For example, when the MN receives the complete RRC connection reconfiguration message, the SN SRB configuration (either SN RRC configuration or direct S-RRC configuration) is considered to be successful.
    [0092] In addition, when the RRC reconfiguration message carries MN RRC configuration information, the UE separately performs the MN configuration and the SN configuration, and returns the configuration results to the MN using the complete reconfiguration message. RRC connection.
    [0093] In step S560, the MN can send the configuration result to the SN using a complete SN reconfiguration message. In addition, the configuration result can be sent to the SN as a container. Alternatively, the complete SN reconfiguration message can be the result of configuration. When the SN receives the complete SN reconfiguration message, the configuration is considered to be successful.
    [0094] Optionally, the MN can analyze the configuration result and, only when the configuration result is successful, it sends data to the terminal to the SN or requests a core network to send data corresponding to the SN. Alternatively, when the configuration result cannot be analyzed by the master node, for example, the configuration result is sent to the master node in a form
    Petition 870190111972, of 11/01/2019, p. 43/100
    38/85 of an RRC container satisfying an SN format requirement, the master node can determine, based on the second indication information, the result of configuring the secondary node's SRB through the terminal and, when the configuration result is successful successful, sends data to the terminal to the SN or requests a core network to send data corresponding to the SN. When the configuration result fails, the MN can reselect an SN for dual connectivity, or modify the SN, or the MN does not send data to the SN, and the SN performs reconfiguration on its own. Here, the data sent by the core network to the SN can be part or all of the data to the terminal. That is, if the core network sends all data to the terminal to the SN it is not limited. The core network can send a part of the data to the SN, and send a part of the data to the MN, so that data download is completed on the core network.
    [0095] After the SN receives the result, sent by the MN, of configuring the SRB of the SN by the terminal, if the SN concludes that the configuration result was successful, the configuration of the SRB in the SN will be completed for the terminal.
    [0096] Furthermore, if the SN RRC configuration result is flawed, the MN can trigger an SN release procedure, that is, send an SN release command with the SN. The SN release command can include indication information indicating that the SN RRC configuration fails.
    [0097] The initial configuration of the dual connectivity is completed by the MN, and the SRB in the SN can be established in an initial configuration process of the dual connectivity. A description is provided below with reference to a drawing
    Petition 870190111972, of 11/01/2019, p. 44/100
    39/85 annex.
    [0098] With reference to Figure 6, Figure 6 is a schematic diagram of a method of establishing a radio carrier according to one embodiment of this application. As shown in Figure 6, the method includes the following steps.
    S610: A RAN 110 node sends an addition request message to an RAN 120 node, where the add request message is used to request the addition of RAN 120 node as an SN.
    [0099] Optionally, the add request message can carry the first indication information in the previous modality, to instruct the RAN 120 node to establish an SRB or generate configuration information for an SRB. Alternatively, the add request message may not carry the first indication information, but instead, when the RAN 120 node receives the add request message, the RAN 120 node establishes a SRB by default, to generate configuration for SRB by default.
    [00100] After the RAN 120 node receives the add request message, the RAN 120 node learns that the RAN 110 node must add the RAN 120 node as an SN and then perform SCG configuration. In this modality, in a process in which the RAN 120 node performs the SCG configuration, the RAN 120 node generates SCG configuration information, and sends the generated SCG configuration information to the RAN 110 node, where the configuration information of SCG carries the configuration information to the SRB (or direct S-RRC configuration information). That is, the RAN 120 node performs the following steps:
    Petition 870190111972, of 11/01/2019, p. 45/100
    40/85
    S620: Ο ηό RAN 120 generates configuration information for an SRB.
    S630: The RAN 120 node adds the configuration information generated for the SRB to an addition request acknowledgment message, and sends the addition request acknowledgment message to the RAN 110 node, where the acknowledgment message add request message is a reply message to the add request message.
    [00101] Like the previous modality, the configuration information for the SRB of the SN can be transported as a container in the acknowledgment message of addition request sent to the MN. For example, configuration information for the SRB can be sent to the MN as an RRC PDU of the SN or a part of the RRC PDU.
    [00102] The RAN 110 node receives the add request acknowledgment message sent by the RAN 120 node, and performs the following operation:
    S640: The RAN 110 node adds the configuration information for the SRB of the RAN 120 node to an RRC connection reconfiguration message, and sends the RRC connection reconfiguration message to a terminal.
    [00103] For example, if the MN is a RAN node in the LTE and the SN is a RAN node in the NR, the MN sends a reconfiguration message of the LTE RRC connection to the terminal. The LTE RRC reconfiguration message includes the configuration information for the SN SRB, for example, it includes the SN RRC PDU, that is, the MN forwards the SN RRC PDU to the terminal. Even when the configuration information for the SN SRB is part of the RRC PDU, the MN can still forward the full RRC PDU to
    Petition 870190111972, of 11/01/2019, p. 46/100
    41/85 the terminal, to send the configuration information to the SN SRB to the terminal.
    [00104] After the terminal receives the RRC connection reconfiguration message, the terminal analyzes the configuration information for the RAN 120 SRB from the RRC connection reconfiguration message, and performs the following operations:
    S650: The terminal configures the SRB of the RAN 120 node using the configuration information for the SRB of the RAN 120 node, for example, establishes an RRC entity and a Layer 2 entity, and enables security processing for direct RRC transmission between the terminal and the SN, to generate a complete RRC connection reconfiguration message. This process is a process of adding the SRB through the terminal, and includes the establishment of a PDCP instance using an SN security configuration, the establishment of an RLC instance based on an RLC configuration, the establishment of a logical channel based on a logical channel configuration, and the like. The instance is a logical unit, and used to perform an operation satisfying a PDCP or RLC layer protocol. Then, step S660 is performed.
    S660: 0 terminal adds a result of configuring the SRB of the RAN 12 0 node for a complete RRC connection reconfiguration complete message, and sends the complete RRC connection reconfiguration message to the RAN 110 node.
    [00105] When the RRC connection reconfiguration message sent by the RAN 110 node includes MN configuration information, the terminal performs the MN configuration separately
    Petition 870190111972, of 11/01/2019, p. 47/100
    42/85 and the SN configuration. The configuration of the MN is performed based on the configuration information of the MN in the reconfiguration message RRC connection, and may include configuration of an SRB and / or DRB or similar of the MN. The SN configuration is performed based on the SN configuration information in the RRC connection reconfiguration message, and includes SN SRB configuration. When the configuration is complete, the terminal can send the MN and SN configuration results to the MN using the complete RRC connection reconfiguration message.
    [00106] Optionally, for the SN configuration result, the terminal can add the second indication information previous to the complete RRC connection reconfiguration message, to indicate the result of configuring the SN SRB through the terminal.
    [00107] The RAN 110 node receives the complete RRC connection reconfiguration message, analyzes the result of configuring the SN SRB by the terminal from the complete RRC connection reconfiguration message, and performs the following step:
    S670: The RAN 110 node sends the configuration result to the RAN 120 node. The RAN 110 node can send the configuration result to the RAN 120 node using a complete SN reconfiguration message.
    [00108] Optionally, the RAN 110 node can send the configuration result to the RAN 120 node in the form of a container. In addition, optionally, the RAN 110 node can analyze the configuration result, and only when the configuration result is successful, send data to the terminal to the RAN 120 node, that is, the SN, or request
    Petition 870190111972, of 11/01/2019, p. 48/100
    43/85 a core network to send data to the terminal to the SN.
    [00109] In this way, the SRB is established in the SN for the terminal.
    [00110] It can be learned that the method shown in Figure 5 can be completed in an initial dual connectivity configuration process. The configuration information for the SN SRB is sent to the MN using the add request acknowledgment message, and sent to the terminal using the MN's RRC connection reconfiguration message. The terminal then configures the SN SRB using the configuration information for the SN SRB, and sends the configuration result to the MN using the complete RRC connection reconfiguration message. The MN sends the configuration result to the SN using the complete SN reconfiguration message. Thus, when the initial configuration of dual connectivity is completed, the SRB is established in the SN at the same time, saving signaling and improving communication efficiency.
    [00111] In addition, the complete RRC connection reconfiguration message can be the result of configuration, and is sent by the terminal to the MN when the configuration is successful. In addition, the complete SN reconfiguration message can be the result of configuration, and is sent by the MN to the SN when configuration is successful.
    [00112] In the modality shown in Figure 6, the SRB with the SN is configured in the initial dual connectivity configuration process. In another mode, an SRB in an SN can be configured separately. For example, only one DRB in SN can be configured in a configuration process
    Petition 870190111972, of 11/01/2019, p. 49/100
    44/85 initial dual connectivity, and in a DC process, an MN or SN triggers the configuration or establishment of the SRB. In addition, SRB in SN can be configured in another configuration process, for example, in a SN modification process. A description is provided below with reference to Figure 7.
    [00113] With reference to Figure 7, Figure 7 is a schematic diagram of a configuration method according to one embodiment of this application. As shown in Figure 7, the method includes the following steps.
    S710: An MN sends a modification request message to an SN, where the modification request message is used to request the modification of an SN configuration, for example, to establish some carriers in the SN, or request to modify an SCG carrier or an SCG portion of a split carrier, or request to add or release an SCG cell. In this mode, the SN is asked to generate configuration information for an SRB, and to allocate a corresponding radio resource.
    [00114] Optionally, the modification request message can carry the first indication information in the previous modality, to instruct the SN to establish the SRB or generate the configuration information for the SRB.
    [00115] After the SN receives the modification request message, the SN analyzes the first indication information, and performs SCG configuration based on the first indication information. In this modality, in a process in which the SN performs SCG configuration, the SN generates information from
    Petition 870190111972, of 11/01/2019, p. 50/100
    45/85 SCG configuration, and sends the generated SCG configuration information to the MN. The SCG configuration information carries the configuration information to the SRB (or direct S-RRC configuration information). That is, the SN performs the following steps:
    S720: 0 SN generates configuration information for an SRB.
    S730: 0 SN adds the configuration information generated for the SRB to a modification request acknowledge message, and sends the modification acknowledgment message to the MN. The change request acknowledgment message is a response message to the change request message.
    [00116] One form or content of the configuration information for the SN SRB is the same as in the previous modality, and the details are not described here again.
    [00117] The MN receives the modification request acknowledgment message sent by the SN, and performs steps S740 to S760. Steps S740 to S760 are similar to steps S640 to S660 in Figure 6, and details are not described here again.
    [00118] In step S760, the MN receives a complete RRC connection reconfiguration message, analyzes the result of configuring the SN SRB by the terminal from the complete RRC connection reconfiguration message, and performs the following step:
    S770: 0 MN sends the configuration result to the SN, where the MN can send the configuration result to the SN using a SN modification confirmation message.
    Petition 870190111972, of 11/01/2019, p. 51/100
    46/85 [00119] Optionally, the MN can send the configuration result to the SN in the form of a container. In addition, optionally, the MN can analyze the configuration result, and only when the configuration result is successful, send data to the terminal to the SN or request a core network to send data to the terminal to the SN.
    [00120] In this way, the SRB is established in the SN for the terminal.
    [00121] The modification of the previous SN is triggered by the MN. Optionally, the SN modification can be triggered by the SN. In this case, unlike the previous modality, before step S710, the method can also include step S701: 0 SN sends a modification required message to the MN, where the required modification message is used to request that the MN allow the SRB to be established between the SN and the terminal or allow an RRC message to be transmitted between the SN and the terminal.
    [00122] Optionally, the required modification message carries indication information, where indication information is used to instruct the MN to send security information used to the SRB from SN to SN.
    [00123] The security information is described in detail in the modality below, and the details are not described here.
    [00124] It can be learned that the method shown in Figure 5 can be completed in dual connectivity, for example, in a SN modification process. The configuration information for the SN SRB is sent to the MN using the change request acknowledgment message, and
    Petition 870190111972, of 11/01/2019, p. 52/100
    47/85 sent to the terminal using the MN RRC connection reconfiguration message. The terminal then configures the SN SRB using the configuration information for the SN SRB, and sends the configuration result to the MN using the complete RRC connection reconfiguration message. The MN sends the configuration result to the SN using the SN modification acknowledgment message. In this way, when an SN modification of dual connectivity is completed, the SRB is established in the SN at the same time, thus saving signaling and improving communication efficiency.
    [00125] In the previous modalities, the MN can still send security information used to the SN SRB (or referred to as security information for direct S-RRC) to the SN. The security information includes at least one of the following: a security key and information about a security algorithm. The security algorithm includes an encryption algorithm and / or an integrity protection algorithm. The information about the security algorithm can be information used to indicate the security algorithm, for example, it can be an indication or an algorithm identifier, or it can be the security algorithm. In this way, SN can perform security processing for SN's SRB using security information, for example, perform encryption / decryption or integrity protection / integrity checking. The MN can send the security information to the SN before the SN generates the configuration information for the SRB, that is, before the MN receives the configuration information for the SN's SRB. After the SN generates the configuration information for the SRB, the SN can perform the
    Petition 870190111972, of 11/01/2019, p. 53/100
    48/85 security processing in the configuration information for the SRB for using the security information, for example, performing integrity protection and / or encryption. If the SRB in the SN is established in an initial dual connectivity setup process, the security information can be carried in the add request message in step S610. If the SRB in the SN is established in a dual connectivity process, the security information can be carried in the modification request message in step S710.
    [00126] Currently, in a MCG split carrier configuration process, the MN does not send the security information to the SN. Because MN transfers a PDCP data packet to SN at a PDCP layer and encryption is completed at the PDCP layer, SN does not need to encrypt data again. However, in this mode, the MN can send the security information to the SN in any scenario, so that the SN performs security processing to the SRB. To be more specific, in the MCG split carrier configuration process, that is, when the MN downloads data to the terminal with the SN in the PDCP layer, the MN still sends the security information to the SN.
    [00127] The security key can be derived based on a root key of the access layer (access stratum, AS) (for example, KeNB) of the MN. For example, when the MN is a RAN node in an LTE system, the security key can be derived from SKeNB based on KeNB. SN selects an encryption / decryption algorithm and an integrity protection / verification algorithm according to a local policy. SN derives, based on the algorithms and the security key
    Petition 870190111972, of 11/01/2019, p. 54/100
    49/85 selected, a key for encryption / decryption and a key for protection / integrity verification, to complete the encryption / decryption and protection / integrity verification in signaling and data packets transported in the SRB and DRB. In the LTE system, an initial AS root key is KeNB. A core network device generates KeNB based on a Kasme root key and a non-access stratum, NAS uplink count, and sends the generated KeNB to the RAN node for the RAN node to calculate an AS security key. The RAN node can derive SKeNB based on KeNB and a COUNT parameter, and send SKeNB to SN. Referring to Figure 8, Figure 8 is a schematic diagram of a COUNT parameter according to one embodiment of this order. As shown in Figure 8, the COUNT parameter includes two parts: a high-order hyper-frame number (Hiper Frame Number, HFN) and a low-order PDCP sequence number (PDCP Sequence Number, PDCP SN).
    [00128] The forms of representation of an AS root key and a key derived from the AS root key are described above using those in the LTE system as an example, but are not limited in this request. For example, when the MN is a base station in the LTE system, the AS root key and the key derived from the AS root key are represented as KeNB and SKeNB. When the MN is a base station in a system of another standard, a different form can be used for representation. For example, in a 5G communication system, the root key of AS and the key derived from root key of AS can be represented as KgNB and SKgNB, or Kcu and SKcu. Of course, other forms of representation can also be
    Petition 870190111972, of 11/01/2019, p. 55/100
    50/85 used and are not listed here, and this request is not limited to forms of representation.
    [00129] After dual connectivity is configured for the terminal, the groups of cells serving are divided into an MCG and an SCG. A cell in the MCG belongs to the MN, and a cell in the SCG belongs to the SN. Carrier aggregation (Carrier Aggregation, CA) can be configured in MCG and / or SCG. In SCG CA, an uplink component carrier (Component Carrier, DC) is configured for at least one cell, including a secondary primary cell (Primary Secondary Cell, PSCell) and a physical uplink control channel (Physical Uplink Control Channel, PUCCH) is configured for PSCell.
    [00130] Currently, the PSCell can only be changed when the SCG is changed, that is, a change of PSCell is accompanied by the change of key and random access processes. However, when the SRB is established in the SN, the SRB exists between the terminal and the SN, and independent measurement can be implemented on the SN side. For example, the SN performs the measurement setup on the terminal using an RRC message, and the terminal performs the measurement and reporting accordingly. In this case, the SN can trigger a PSCell change by itself, and the PSCell change is accompanied by the key update.
    [00131] Based on this, in one mode, the SN can send a request message to the MN and then the MN sends an updated key to the SN and the terminal, where the request message is used to request the updated key from MN. This process causes a specific latency.
    Petition 870190111972, of 11/01/2019, p. 56/100
    51/85 [00132] As the SRB can be established in the SN, configuration can be performed directly between the SN and the terminal. In this way, quick configuration can be implemented. In addition, if the SN can update a key by itself, configuration efficiency in the SN can be further improved.
    [00133] Based on this, in another modality, the MN can send a group of keys (or a list of keys (key list)) to SN so that SN selects a key from the group of keys when updating a key. Optionally, the group of keys can be carried in the request message in step S502 in Figure 5, or the add request message in step S610 in Figure 6, or the change request message in step S710 in Figure 7. In addition , the MN can send the group of keys based on an SN instruction. For example, the SN sends indication information to the MN, to instruct the MN to send the group of keys to the SN. Referral information can be sent separately, or can be carried in another message. For example, at step S701 in Figure 7, the SN can send the indication information to the MN. Of course, the MN may not need to send the key group based on an SN instruction, but actively trigger the key group submission.
    [00134] In an implementation, the MN sends, to the SN, the group of keys and a group of count values (COUNT), that is, a group of count values (or referred to as list of count values, list COUNT) used to derive keys in the key group. The SN receives the group of keys and the group of count values, and selects a new key, that is, a key other than a key.
    Petition 870190111972, of 11/01/2019, p. 57/100
    52/85 key group when a key needs to be updated. The SN then sends a count value used to derive the key to the terminal, so that the terminal completes the synchronous key update.
    [00135] SN can select the key sequentially or randomly. When the SN selects the key sequentially, the MN may not send the group of count values to the SN, and send the group of count values to the terminal. When the SN updates the key, the SN sends notification information to the terminal to instruct the terminal to update the key, and the terminal sequentially uses a count value to update the synchronous key. Alternatively, the association information can be defined for a key and a count value used to derive the key, to associate the key with the count value. For example, the same sequence number is defined for the key and the count value. When the SN randomly selects the key, association information for the selected key is sent to the terminal, so that the terminal accordingly selects the corresponding count value for synchronous key update.
    [00136] The key here is a derived key, derived from a root key and a count value. A description of the key is the same as in the previous modality, and the details are not described here again.
    [00137] In addition, in the previous modes, when the terminal performs MN RRC configuration, but cannot perform SN SRB configuration (either RRC configuration or direct S-RRC configuration), the terminal can send fault information from configuration from SN SRB to MN. Beyond
    Petition 870190111972, of 11/01/2019, p. 58/100
    In addition, the terminal can send an RRC connection reinstatement request message to the SN, where the RRC connection reestablishment request message can be carried in the complete RRC connection reconfiguration message sent to the MN. After the MN receives the complete RRC connection reconfiguration message, the MN sends a modification request message to the SN, and adds the RRC connection reestablishment request message to the modification request message.
    [00138] After the SN SRB configuration is completed, the SN can directly send an RRC connection reconfiguration message to the terminal for configuration. When the terminal cannot perform the RRC configuration, the terminal triggers a process of reestablishing RRC connection between the terminal and the SN according to the prior art, but the process interrupts the transmission of data carried in the SN. In view of this problem, in a mode of this request, the terminal restores configuration before the RRC connection reconfiguration message is received, that is, it works based on the configuration before the RRC connection reconfiguration message is received, does not trigger connection reconnection. RRC, and notify SN that the most recent configuration fails. The terminal can notify, directly or through the MN, the SN that the most recent configuration fails.
    [00139] Still referring to Figure 4, when the SRB is established in the SN to transmit an RRC message between the SN and the terminal, the RRC messages between the terminal and a RAN may include an RRC message from the MN (ie, a message M-RRC) and an RRC message from SN (ie an SRRC message). A downlink S-RRC message (ie an
    Petition 870190111972, of 11/01/2019, p. 59/100
    54/85 RRC message sent by SN to the terminal) includes a direct S-RRC message and a built-in S-RRC message. An RRC message (for example, an RRC connection reconfiguration message) that is not related to the negotiation between the SN and the MN can be sent directly by the SN to the terminal, or it can be sent to the terminal via the MN. That is, an RRC message of a direct S-RRC type can be used, or an RRC message of an embedded S-RRC type can be used. A specific way or message to be used can be determined by the SN.
    [00140] There are also two possibilities to send an S-RRC uplink message. That is, uplink S-RRC messages (i.e., RRC messages sent by the terminal to the SN) include a direct S-RRC message and an embedded S-RRC message. When the terminal uses both the direct S-RRC message and the embedded S-RRC message, a network side problem can be caused. For example, the reliability of uplink RRC message transmission decreases. For example, after the terminal sends a measurement report using the built-in S-RRC message, the terminal sends, in a short time, another measurement report using the direct S-RRC message. However, due to an overhead latency of the MN and an interface latency between the MN and the SN, the measurement report sent using the built-in S-RRC message can reach the SN later than the measurement report sent using the direct S-RRC message. Consequently, the SN cannot use the measurement result.
    [00141] In view of this, the modalities of this request provide the following method of transmission of RRC message,
    Petition 870190111972, of 11/01/2019, p. 60/100
    55/85 to improve the reliability of uplink RRC message transmission.
    [00142] In a first method, uplink and downlink paths are the same. This method is applicable to a case in which an uplink RRC message to an SN sent by a terminal is a response message to an SN downlink RRC message. For example, a complete RRC connection reset message is a response message for an RRC connection reset message. In this case, the terminal sends the uplink RRC message on the same path as the downlink RRC message.
    [00143] With reference to Figure 9, Figure 9 is a schematic diagram of a RRC transmission method according to one embodiment of this request. As shown in Figure 9, the method is applied to a communications system, where the communications system includes an MN and an SN that jointly provide a service for a terminal, and the method includes the following steps:
    S910: The terminal receives a downlink RRC message from the SN, where the downlink RRC message is received by the MN from the MN and sent to the terminal (a path shown by a dashed line in the figure), or the downlink RRC message. is sent by SN to the terminal (a path shown by a solid line in the figure).
    S920: The terminal sends an uplink RRC message, where the uplink RRC message is a response message to the uplink RRC message, and a path in which the terminal sends the uplink RRC message is equal to the path in which the
    Petition 870190111972, of 11/01/2019, p. 61/100
    56/85 terminal receives downlink link RRC message. To be specific, when the downlink RRC message is received by the MN from the SN and sent to the terminal, the uplink RRC message is sent by the terminal to the MN and sent by the MN to the SN (a path shown by a dotted line in the figure ). Alternatively, when the downlink RRC message is sent by the SN to the terminal, the uplink RRC message is sent by the terminal to the SN (a path shown by a solid line in the figure). 0 sent here means to be sent directly without being forwarded by the MN.
    [00144] It can be learned that the terminal sends the uplink RRC message in a path consistent with a path in which the SN downlink RRC message is received. In this way, a problem of poor reliability of the uplink RRC message caused by sending in two paths is solved.
    [00145] In a second method, an MN or an SN configures an uplink RRC transmission path. This method can be applied to a case where a terminal initiates (initiate) an uplink RRC message, and it can also be applied to a case where an uplink RRC message to an SN sent by a terminal is an response to an SN downlink RRC message.
    [00146] For example, an MN configures an uplink RRC transmission path. Referring to Figure 10, Figure 10 is a schematic diagram of another method of transmitting RRC according to one embodiment of this application. As shown in Figure 10, the method is applied
    Petition 870190111972, of 11/01/2019, p. 62/100
    57/85 to a communications system, where the communications system includes an MN and an SN that jointly provide a service to a terminal, and the method includes the following steps.
    S1010: 0 MN generates SN uplink RRC configuration information, where uplink RRC configuration information is used to configure a way in which the terminal sends an uplink RRC message to SN.
    S1020: 0 MN sends uplink RRC configuration information to the terminal, so that the terminal sends uplink RRC messages based on uplink RRC configuration information.
    [00147] The terminal receives the uplink RRC configuration information, and performs the following step:
    S1030: The terminal sends an uplink RRC message to the SN based on the uplink RRC configuration information.
    [00148] Uplink RRC configuration information can be sent to the terminal in the process shown in Figure 5 of establishing the SRB of the secondary node, or it can be sent to the terminal after the process shown in Figure 5 of establishing the SRB of the node secondary, that is, after the secondary node's SRB is established, and the MN can add the uplink RRC configuration information to an RRC connection reconfiguration message.
    [00149] Alternatively, an SN can configure an uplink RRC transmission path, that is, the way of sending the uplink RRC message can be configured by the SN. In this case, step S1010 can be: obtain, through the MN, link RRC configuration information
    Petition 870190111972, of 11/01/2019, p. 63/100
    58/85 upward from SN. Optionally, the uplink RRC configuration information can be included in the previous configuration information for the SRB. In addition, possible configurations in the uplink RRC configuration information include:
    1. A reply message (or referred to as a replica message) for an RRC message sent by the SN is sent directly to the SN. That is, the terminal directly sends an uplink RRC message to the SN to the SN, where the uplink RRC message is a response message to an SN downlink RRC message.
    2. A reply message (or referred to as a replica message) for an RRC message sent by the SN is sent to the SN via the MN. That is, the terminal directly sends an uplink RRC message to the SN to the MN, and the MN sends the uplink RRC message to the SN to the SN, where the uplink RRC message is a response message for a message SN downlink RRC. In this case, the terminal sends an RRC message to the MN in the format of a pattern to which the MN belongs, that is, an M-RRC message. The M-RRC message includes an RRC message returned by the terminal to the SN, and is in the format of a pattern to which the SN belongs, that is, a message ΞΗΡΟ incorporated. For example, if the MN is an LTE eNB and the SN is a NR gNB, after the SN sends a NR RRC connection reconfiguration message to the UE, the terminal generates a complete NR RRC connection reconfiguration message after configuration. The complete NR RRC connection reconfiguration message is sent to the MN using an LTE RRC message
    Petition 870190111972, of 11/01/2019, p. 64/100
    59/85 and then sent by the MN to the SN.
    3. The terminal sends, based on the measurement result of an SN cell, an upstream link RRC message to the SN to the SN directly or through the MN. For example, a measurement threshold is set for the terminal. When a measurement value obtained by the terminal by measuring the SN cell is greater than the threshold, the terminal directly sends the uplink RRC message to the SN to the SN. Otherwise, the terminal adds the uplink RRC message to the SN for an RRC message sent to the MN, to send the uplink RRC message to the SN to the MN, and the MN sends the uplink RRC message to the SN to SN.
    4. It is configured that a first type uplink RRC message to the SN is sent directly to the SN and a second type uplink RRC message to the SN is sent to the SN via the MN. SN's first and second type uplink RRC messages can include more than one message type, and can be configured specifically based on a requirement, and are not limited here.
    5. A rule that the uplink is subordinate to the downlink is configured. If a downlink RRC message is received at the SN SRB, a corresponding uplink RRC message is also sent at the SN SRB, that is, the terminal sends the uplink RRC message to the SN on the same path as the message. SN downlink RRC. Optionally, the uplink RRC message is a response message for the uplink RRC message, similar to the modality
    Petition 870190111972, of 11/01/2019, p. 65/100
    60/85 shown in Figure 9. The modality shown in Figure 9 can be implemented through an agreement between the terminal and a network side without configuration by the MN, or it can be implemented through the configuration by the MN.
    6. An uplink RRC message to the SN does not affect the MN by default, and is sent directly to the SN SRB, that is, the terminal directly sends the uplink RRC message to the SN to the SN. Alternatively, an uplink RRC message to the SN affects the MN by default, and is sent to the SN via the MN, that is, the terminal sends the uplink RRC message to the SN to the SN through the MN.
    [00150] Regardless of uplink or downlink, in a scenario where the MN sends an RRC message from SN to SN, a tunnel is established between the MN and SN to transmit an RRC message sent by the terminal to SN. For example, an SRB SCG can be indicated in an SN request request message, and an acknowledgment message returned by the SN to the MN carries a tunnel endpoint identifier (TEID) allocated to the SCG SRB.
    [00151] It should be noted that the mode shown in Figure 9 or Figure 10 can be combined with the previous mode, to further improve the reliability of the uplink RRC message transmission.
    [00152] In a scenario of dual LTE-NR connectivity in which LTE is used as an anchor, if an SN works at high frequency, a beam forming technology can be used. A terminal may need to measure and report a beam in the SN, to select a suitable beam for the
    Petition 870190111972, of 11/01/2019, p. 66/100
    61/85 terminal. Currently, both the configuration and the measurement report of the terminal are performed on an MN. To be more specific, the MN performs the measurement configuration for the terminal, and the terminal performs measurement based on the measurement configuration, and sends a measurement report to the MN when a measurement event is satisfied. Therefore, in the LTE-NR dual connectivity scenario, if the existing way is still used, the movement of the terminal between cells or bundles of the SN needs to be controlled by the MN. When the MN determines to change a cell or beam, the MN notifies the terminal, and the MN still needs to notify the SN, to implement the movement of the terminal in the SN.
    [00153] It can be learned that a time required by an entire configuration process includes an air interface transmission time between the LTE standard MN and the terminal and an interface interaction time between the MN and the SN. Compared to a case where the configuration and interaction are implemented directly between the SN and the terminal, the existing mechanism has a longer latency. In a high frequency motion scenario, it is possible that the existing mechanism cannot satisfy a low latency requirement. In the previous modalities, an RRC message can be transmitted directly between the terminal and the SN, that is, the SN can establish an SRB for communication with the terminal. In this case, the MN can configure only the LTE measurement for the terminal, and the NR measurement is configured by the SN. If the MN and SN configure the NR measurement for the terminal, a problem such as inconsistent configuration can be caused. The MN can also learn from information about a surrounding NR cell, to implement SCG switching or management.
    Petition 870190111972, of 11/01/2019, p. 67/100
    62/85
    To further improve the mobility management efficiency, in an embodiment of this request, an MN sends measurement configuration information to an SN, where the measurement configuration information is used to configure a condition to trigger the SN to send, to the MN, a result of measuring an SN cell by a terminal. For example, the measurement configuration information is a threshold. When a measurement result in a measurement report received by the SN is greater than or equal to the threshold, the SN sends the measurement result to the MN, so that the MN performs mobility management, for example, makes a switching decision or performs SCG management.
    [00154] With reference to Figure 11, Figure 11 is a schematic diagram of a configuration method according to one embodiment of this application. As shown in Figure 11, the method is applied to a communications system, where the communications system includes an MN and an SN that jointly provide a service for a terminal, measurement of an MN cell by the terminal is configured by the MN, measurement of an SN cell through the terminal is configured by the SN, and the method includes the following steps:
    [00155] S1110: The MN sends measurement configuration information to the SN, where the measurement configuration information is used to configure a condition to trigger the SN to send a measurement result to the MN.
    [00156] S1120: The SN receives a measurement report which is obtained by measuring a cell of the SN and which is sent by the terminal.
    [00157] S1130: When the measurement report includes a measurement result satisfying the previous condition, the SN
    Petition 870190111972, of 11/01/2019, p. 68/100
    63/85 sends the measurement result to the MN.
    [00158] Certainly, the SN can send all measurement results in all measurement reports to the MN, or it can send only one measurement result satisfying the condition. This is not limited here.
    [00159] The measurement configuration information may include a threshold. When a measurement result in a measurement report obtained by the SN is greater than or equal to the threshold, the SN sends the measurement result to the MN. That is, step S1110 can be: send, through the MN, a threshold for the SN. Step S1130 can be: when a measurement result in the measurement report is greater than or equal to the threshold, send the measurement result to the MN via SN. Optionally, the SN can send all measurement results to the MN, or send some measurement results to the MN. For example, a measurement value greater than or equal to the threshold is sent to the MN. In addition, the information sent by the SN can also include a cell / beam identifier corresponding to the measurement result sent.
    [00160] In addition, the SN can also configure the threshold for the terminal as a measurement threshold. Alternatively, the SN can configure, for the terminal, another measurement threshold other than the threshold. That is, the SN can configure a measurement event for the terminal with reference to the threshold. For example, the SN can configure, for the terminal as a threshold of the measurement event, the threshold obtained from the MN. Alternatively, the SN can set a measurement threshold for the terminal itself, without reference to the threshold.
    [00161] For example, the MN is an LTE eNB and the SN is an NR gNB. After completing the initial setup, only the
    Petition 870190111972, of 11/01/2019, p. 69/100
    64/85 LTE measurement is implemented between the MN and the terminal, and the NR measurement configuration and reports are performed between the SN and the terminal. To allow the MN to learn about NR measurement to implement mobility management (for example, MN switching or SN switching), the MN can obtain a required measurement result from the SN. For example, the MN can configure a threshold for the SN. The threshold may be a reference signal received power threshold (Reference Signal Received Power, RSRP), a reference signal received quality threshold (Reference Signal Received Quality, RSRQ) or similar. The threshold can be carried in an SN add / modify request message and sent to the SN. The SN receives a measurement report reported by the terminal. The measurement report includes a result of measuring an NR cell and / or beam, for example, includes a measurement value, such as RSRP or RSRQ of the NR cell or beam. When a measurement result from an NR cell or beam exceeds the threshold set by the MN, the SN sends measurement information to the MN. The measurement information includes an identifier and a measurement result from at least one NR cell / beam.
    [00162] It should be noted that this modality can be combined with the previous modality, to further improve the efficiency of managing terminal mobility.
    [00163] With reference to Figure 12, Figure 12 is a schematic diagram of an apparatus according to an embodiment of this application. Device 1200 is applied to an SN in a communications system. The communications system includes an MN and an SN that jointly provide a service to a terminal. As shown in Figure 12, the device
    Petition 870190111972, of 11/01/2019, p. 70/100
    65/85
    1200 includes units or means (means) for executing steps performed by an SN in any method modality of the previous method, and all detailed descriptions of those steps are applicable to this device modality. For example, apparatus 1200 includes a first communications unit 1210 and a second communications unit 1220. The first communications unit 1210 is configured to control communication between the SN and the MN and can include a first receiving unit and a first unit which are configured respectively to control reception and sending. The first communications unit 1210 can receive and send messages via an interface (for example, an X2 interface, which can also be referred to as an Xn interface) between the SN and the MN. The second communications unit 1220 is configured to control communication between the SN and the terminal and can include a second receiving unit and a second sending unit which are configured respectively to control the receiving and sending. The second communications unit 1220 can receive and send messages via an interface (e.g., an air interface) between the SN and the terminal. The interface here is a logical concept, and a corresponding logical unit needs to be defined during implementation to satisfy a protocol requirement for a corresponding interface. A physical connection between nodes can be a wireless or wired connection. For example, a wireless connection can be used for a RAN node (the MN or
    SN) and terminal, is way of connection with wire can be used for the SN and the MN. [00164 ] In the modalities of method previous, all
    Petition 870190111972, of 11/01/2019, p. 71/100
    66/85 messages or information received by the SN from the MN can be received under control of the first communications unit 1210, and all messages or information sent by the SN to the MN can be sent under control of the first communications unit 1210. All messages or information received by the SN from the terminal can be received under the control of the second communications unit 1220 and all messages or information sent by the SN to the terminal can be sent under control of the second communications unit 1220.
    [00165] For example, the previous device 1200 can be a configuration device, and also includes a generation unit 1230, configured to generate configuration information for an SRB, where the SRB is used to transmit an RRC message between the SN and the terminal. The first communications unit 1210 is configured to send the configuration information to the SRB to the MN, so that the configuration information to the SRB is sent to the terminal via the MN. When the terminal sends a configuration result to the SN via the MN, the first communications unit 1210 is configured to receive a result of configuring the SRB by the terminal for using the configuration information for the SRB. When the terminal sends a configuration result directly to the SN, the second communications unit 1220 is configured to receive a result of configuring the SRB by the terminal for using the configuration information for the SRB.
    [00166] For descriptions of the cases in which the 1230 generation unit generates configuration information for the SRB, and forms and content of the configuration information for
    Petition 870190111972, of 11/01/2019, p. 72/100
    67/85 to SRB, see the previous modalities, and the details are not described here again. In addition, for details on other messages or information sent or received, see the previous method modalities and the details are not described here again. In addition, for content or forms of messages or information sent or received, please also refer to the previous method modalities.
    [00167] Optionally, the first communications unit 1210 is further configured to receive security information used for the SN SRB from the MN. In this case, the device 1200 may also include a security processing unit 1240, configured for: before the configuration information for the SRB is
    sent to MN, perform Processing safety at information configuration for SRB's SN using The information of security. [00168] Optionally, the first unity in
    communications 1210 is further configured to receive a group of keys from the master node. In this case, the device 1200 may also include a selection unit 1250, configured to select a key from the group of keys when the SN updates a key.
    [00169] For another example, the previous device 1200 can be another configuration device. The first communications unit 1210 is configured to receive measurement configuration information from the MN, where the measurement configuration information is used to configure a condition to trigger the SN to send a measurement result to the MN. The second communications unit 1220 is configured to receive a report from the terminal
    Petition 870190111972, of 11/01/2019, p. 73/100
    68/85 of measurement obtained by the terminal for measuring a cell of the SN. When the measurement report includes a measurement result satisfying the previous condition, the first communication unit 1210 is configured to send the measurement result to the MN.
    [00170] It should be understood that the division of the units of the preceding apparatus is merely division of logical functions. During actual implementation, all or some of the units can be integrated into a physical entity or can be physically separated. In addition, these units can all be implemented in a form of software invoked by a processing element, or they can be implemented in hardware, or some units can be implemented in a form of software invoked by a processing element, and some units can implemented by hardware. For example, during implementation, the first communications unit 1210 can be a separately arranged processing element, or it can be integrated with an SN chip. Alternatively, the first communications unit 1210 can be stored in an SN memory as a program and invoked by an SN processing element to perform a function of the unit. The implementation of other units is similar to this. In addition, all or some of these units can be integrated or implemented separately. The processing element here can be an integrated circuit with a signal processing capability. In an implementation process, the steps of the previous method or the previous units can be completed using a hardware integrated logic in a processor element or instructions in a
    Petition 870190111972, of 11/01/2019, p. 74/100
    69/85 software form. In addition, the first previous communications unit is a communication control unit, and can receive information sent by the MN or send information to the MN via a connection medium, for example, an optical fiber, between the SN and the MN. The second second communication unit is a communication control unit, and can receive information sent by the terminal or send information to the terminal through a receiving device, for example, an antenna and a radio frequency device, from SN.
    [00171] For example, the previous units can be configured as one or more integrated circuits to implement the previous method, for example, one or more application specific integrated circuits (ApplicationSpecific Integrated Circuit, ASIC) or one or more microprocessors (digital signal processor, DSP) or one or more arrays of programmable field gates (FieldProgrammable Gate Array, FPGA). For another example, when a unit above is implemented in a form of a program scaled by a processing element, the processing element can be a general purpose processor, for example, a central processing unit (Central Processing Unit, a CPU) or another processor that can invoke a program. For another example, these units can be integrated, and implemented as a system on a chip (system-on-a-chip, SOC).
    [00172] With reference to Figure 13, Figure 13 is a schematic diagram of an apparatus according to an embodiment of this application. The 1300 device is applied to an MN in a communications system. The communications system
    Petition 870190111972, of 11/01/2019, p. 75/100
    70/85 includes the MN and an SN that jointly provide a service for a terminal. As shown in Figure 13, apparatus 1300 includes units or means (means) for carrying out the steps performed by an MN in any method modality of the previous method, and all detailed descriptions of those steps are applicable to this apparatus modality. The apparatus 1300 includes a first receiving unit 1310, a first sending unit 1320, a second receiving unit 1330 and a second sending unit 1340. The first receiving unit 1310 and the first sending unit 1320 can be referred to as a first communications unit, configured to control the communication between the MN and the SN; and it can receive and send messages through an interface (for example, an X2 interface, which can also be called an Xn interface) between the MN and the SN. The second receiving unit 1330 and the second sending unit 1340 can be referred to as a second communications unit, configured to control communication between the MN and the terminal; and it can receive and send messages through an interface (for example, an air interface) between the MN and the terminal. The interface here is a logical concept, and a corresponding logical unit needs to be defined during implementation to satisfy a protocol requirement for a corresponding interface. A physical connection between nodes can be a wireless or wired connection. For example, a wireless connection way can be used for a RAN node (the MN or SN) and the terminal, and a wired connection way can be used for the MN and SN.
    [00173] In the previous method modalities, all the
    Petition 870190111972, of 11/01/2019, p. 76/100
    71/85 messages or information received by the MN from the SN can be received under control of the first receiving unit 1310, and all messages or information sent by the MN to the SN can be sent under control of the first sending unit 1320. All messages or information received by the MN from the terminal can be received under control of the second receiving unit 1330 and all messages or information sent by the MN to the terminal can be sent under control of the second sending unit 1340.
    [00174] For example, the first receiving unit 1310 is configured to receive configuration information for an SRB from the SN, where the SRB is used to transmit an RRC message between the SN and the terminal. To transmit here means to transmit directly without forwarding through the MN. The second sending unit 1340 is configured to send the configuration information to the SRB to the terminal. The second receiving unit 1330 is configured to receive a result of configuring the SRB through the terminal by using the configuration information for the SRB. The first 1320 sending unit is configured to send the configuration result to the SN. For details on other messages or information sent or received, refer to the previous method modalities, and the details are not described here again. In addition, for content or forms of messages or information sent or received, please also refer to the previous method modalities.
    [00175] For another example, the previous device is an RRC message transmission device, and also includes a 1350 generation unit, configured to generate SN uplink RRC configuration information, or the
    Petition 870190111972, of 11/01/2019, p. 77/100
    72/85 first receiving unit 1310 is configured to receive uplink RRC configuration information from the SN. The uplink RRC configuration information is used to configure a way in which the terminal sends an uplink RRC message to the SN. The second sending unit 1340 is configured to send uplink RRC configuration information to the terminal, so that the terminal sends uplink RRC messages based on the uplink RRC configuration information. The way of sending is the same as the previous modalities, and the details are not described here again.
    [00176] For another example, the previous device is a configuration device. The first sending unit 1320 is configured to send measurement configuration information to the SN, where the measurement configuration information is used to configure a condition to trigger the SN to send a measurement result to the MN. The first receiving unit 1310 receives a measurement result satisfying the previous condition from the SN, where the measurement result is obtained by the terminal by measuring a cell in the SN and reported to the SN.
    [00177] It should be understood that the division of the units of the preceding device is merely division of logical functions. During actual implementation, all or some of the units can be integrated into a physical entity or can be physically separated. In addition, these units can all be implemented in a form of software invoked by a processing element, or they can be implemented by hardware, or some units can be implemented in one
    Petition 870190111972, of 11/01/2019, p. 78/100
    73/85 form of software invoked by a processing element, and some units can be implemented by hardware. For example, during implementation, the first receiving unit 1310 may be a separately arranged processing element or may be integrated with an MN chip. Alternatively, the first receiving unit 1310 can be stored in the memory of the MN as a program and invoked by a processing element of the MN to perform a function of the unit. The implementation of other units is similar to this. In addition, all or some of these units can be integrated or implemented separately. The processing element here can be an integrated circuit with a signal processing capability. In an implementation process, the steps of the previous method or the previous units can be completed using a logic integrated circuit to the hardware in a processor element or instructions in a software form. In addition, the first previous receiving unit is a receiving control unit and can receive, via a receiving device, for example, an antenna and a radio frequency device, from the MN, information sent by the terminal. The first previous sending unit is a sending control unit and can send information to the terminal through a transmission device, for example, an antenna and a radio frequency device, from the MN. The second previous receiving unit is a receiving control unit and can receive, via a connection medium, for example, an optical fiber, between the MN and the SN, information sent by the SN. The previous second shipping unit is a shipping control unit and can send
    Petition 870190111972, of 11/01/2019, p. 79/100
    74/85 information to the SN through a means of connection, for example, an optical fiber, between the MN and the SN.
    [00178] For example, the previous units can be configured as one or more integrated circuits to implement the previous method, for example, one or more integrated circuits of specific application (ApplicationSpecific Integrated Circuit, ASIC), or one or more microprocessors (digital signal processor, DSP) or one or more arrays of programmable field gates (FieldProgrammable Gate Array, FPGA). For another example, when a unit above is implemented in a form of a program scaled by a processing element, the processing element can be a general purpose processor, for example, a central processing unit (Central Processing Unit, a CPU) or another processor that can invoke a program. For another example, these units can be integrated, and implemented as a system on a chip (system-on-a-chip, SOC).
    [00179] With reference to Figure 14, Figure 14 is a schematic diagram of an apparatus according to an embodiment of this application. The device 1400 is applied to a terminal in a communications system. The communications system includes an MN and an SN that jointly provide a service to the terminal. As shown in Figure 14, apparatus 1400 includes units or means (means) for executing the steps performed by a terminal in any method modality of the previous method, and all detailed descriptions of those steps are applicable to this apparatus modality. The device includes a receiving unit 1410 and a sending unit 1420. The
    Petition 870190111972, of 11/01/2019, p. 80/100
    75/85 reception 1410 and sending unit 1420 are configured to control communication with a RAN node (for example, MN or SN), and can receive and send messages through an interface (for example, an air interface) between the terminal and the RAN node. The interface here is a logical concept, and a corresponding logical unit needs to be defined during implementation to satisfy a protocol requirement for a corresponding interface. A physical connection between nodes can be a wireless connection.
    [00180] In the previous method modalities, all messages or information received by the MN or SN terminal can be received under control of the receiving unit 1410, and all messages or information sent by the terminal to the MN or SN can be sent under control of the shipping unit 1420.
    [00181] For example, the previous device 1400 is a configuration device, and also includes a configuration unit 1430. The receiving unit 1410 is configured to receive configuration information for an SN SRB from the MN, where the SRB is used to transmit an RRC message between the SN and the terminal. To transmit here means to transmit directly without forwarding through the MN. The configuration unit 1430 is configured to configure the SRB by using the configuration information for the SRB. The sending unit 1420 is configured to send a result of configuring the SRB. For details on other messages or information sent or received, refer to the previous method modalities, and the details are not described here again. In addition, for content or forms of messages or information sent or received, see
    Petition 870190111972, of 11/01/2019, p. 81/100
    76/85 also the previous method modalities.
    [00182] In addition, configuration unit 1430 can be further configured to perform another RRC configuration. For example, after the SRB configuration is completed, the receiving unit 1410 may receive an RRC connection reconfiguration message from the SN. In this case, the configuration unit 1430 can perform reconfiguration corresponding to the RRC connection reconfiguration message. In addition, when reconfiguration fails, the configuration unit 1430 can restore configuration before the RRC connection reconfiguration message is received.
    [00183] For another example, the previous device is an RRC message transmission device. The receiving unit 1410 is configured to receive a downlink RRC message from the SN, where the downlink RRC message is received by the MN from the SN and sent to the terminal, or the downlink RRC message is sent by the SN to the terminal. Sending unit 1420 is configured to send an uplink RRC message, where the uplink RRC message is a response message to the downlink RRC message, and a path in which sending unit 1420 sends the RRC message. uplink is the same as a path in which the receiving unit 1410 receives the downlink RRC message. That is, when the downlink RRC message is received by the MN from the SN and sent to the terminal, the uplink RRC message is sent by the terminal to the MN and sent by the MN to the SN. Alternatively, when the downlink RRC message is sent by the SN to the terminal, the uplink RRC message is sent by the SN
    Petition 870190111972, of 11/01/2019, p. 82/100
    77/85 terminal to the SN.
    [00184] For another example, the previous device is an RRC message transmission device. Receiving unit 1410 is configured to receive SN uplink RRC configuration information from the MN, where uplink RRC configuration information is used to configure a way in which the terminal sends a link RRC message ascending to the SN. Sending unit 1420 is configured to send the uplink RRC message to the SN based on uplink RRC configuration information. The way of sending is the same as the previous modalities, and the details are not described here again.
    [00185] It should be understood that the division of the units of the previous device is merely division of logical functions. During actual implementation, all or some of the units can be integrated into a physical entity or can be physically separated. In addition, these units can all be implemented in a form of software invoked by a processing element, or they can be implemented in hardware, or some units can be implemented in a form of software invoked by a processing element, and some units can implemented by hardware. For example, during implementation, the receiving unit 1410 may be a separately arranged processing element or may be integrated with a terminal chip. Alternatively, the receiving unit 1410 can be stored in the terminal's memory as a program and invoked by a terminal processing element to perform a function of the unit. The implementation of other units is
    Petition 870190111972, of 11/01/2019, p. 83/100
    78/85 similar to this. In addition, all or some of these units can be integrated or implemented separately. The processing element here can be an integrated circuit with a signal processing capability. In an implementation process, the steps of the previous method or the previous units can be completed using a logic integrated circuit to the hardware in a processor element or instructions in a software form. In addition, the receiving unit is a receiving control unit and can receive, via a receiving device, for example, an antenna and a radio frequency device, from the terminal, information sent by MN or SN. The sending unit is a sending control unit and can send information to the MN or SN through a transmission device, for example, an antenna and a radio frequency device, from the terminal.
    [00186] For example, the previous units can be configured as one or more integrated circuits to implement the previous method, for example, one or more application specific integrated circuits (ApplicationSpecific Integrated Circuit, ASIC), or one or more microprocessors (digital signal processor, DSP), or one or more arrays of programmable field gates (FieldProgrammable Gate Array, FPGA). For another example, when a unit above is implemented in a form of a program scaled by a processing element, the processing element can be a general purpose processor, for example, a central processing unit (Central Processing Unit, a CPU) or another processor that can invoke a program. For another example, these units can be
    Petition 870190111972, of 11/01/2019, p. 84/100
    79/85 integrated, and implemented as a system on a chip (system-on-a-chip, SOC).
    [00187] With reference to Figure 15, Figure 15 is a schematic structural diagram of a RAN node according to an embodiment of this request. The RAN node can be the SN or the MN in the previous mode, configured to implement operations of the SN or the MN in the previous mode. As shown in Figure 15, the RAN node includes: an antenna 1510, a radio frequency device 1520 and a base band device 1530. Antenna 1510 is connected to the radio frequency device 1520. In an uplink direction, the radio frequency apparatus 1520 receives, via antenna 1510, information sent by a terminal, and sends the information sent by the terminal to the base band apparatus 1530 for processing. In a downlink direction, the baseband device 1530 processes the information from the terminal, and sends the information from the terminal to the radio frequency device 1520, and the radio frequency device 1520 processes the information from the terminal, and then sends the information from the terminal to the terminal via antenna 1510. Communication between RAN nodes, for example, between an MN and an SN, can be carried out through a transmission medium. The transmission medium can be a wired medium, for example, an optical fiber; or it can be a wireless medium.
    [00188] The device of previous configuration applied to SN or MN can be located in the base band device 1530. In an implementation, the units shown in Figure 12 or Figure 13 are implemented in the form of a program scaled by a processing element . For example, the base band device 1530 includes an
    Petition 870190111972, of 11/01/2019, p. 85/100
    80/85 processing 1531 and a storage element 1532. Processing element 1531 invokes a program stored in storage element 1532, to execute a method executed by SN or MN in the previous method embodiments. In addition, the base band apparatus 1530 may also include an interface 1533, configured to exchange information with the radio frequency apparatus 1520. The interface is, for example, a common public radio interface (CPRI) .
    [00189] In another implementation, the units shown in Figure 12 or Figure 13 can be configured as one or more processing elements to implement a method performed by SN or MN. These processing elements are arranged in the base band apparatus 1530. The processing elements described herein can be an integrated circuit, for example, one or more ASICs, or one or more DSPs, or one or more FPGAs. These integrated circuits can be integrated to form a chip.
    [00190] For example, the units shown in Figure 12 or Figure 13 can be integrated and implemented as a system on a chip (system-on-a-chip, SOC). For example, the base band device 1530 includes a SOC chip, configured to implement the previous method. The chip can be integrated with the processing element 1531 and the storage element 1532, and the processing element 1531 invokes a program stored in the storage element 1532 to implement the previous method performed by the SN or the MN or functions of the units shown in Figure 12 or Figure 13. Alternatively, the chip can be integrated with at least one integrated circuit, to implement the method performed
    Petition 870190111972, of 11/01/2019, p. 86/100
    81/85 by SN or MN or unit functions shown in Figure 12 or Figure 13. Alternatively, previous implementations can be combined, where functions of some units are implemented by the processing element, invoking a program, and the functions of some units are implemented by an integrated circuit.
    [00191] Regardless of the ways used, the previous configuration device applied to SN or MN includes at least one processing element, and a storage element, where at least one processing element is configured to execute the method that it is carried out by the SN or the MN and provided in the previous method modalities. The processing element can execute, in a first way, that is, by executing a program stored in the storage element, some or all of the steps performed by SN or MN in the previous method modalities; or it can execute, in a second way, that is, using a logic integrated circuit to the hardware in a processor element and instructions, some or all of the steps performed by SN or MN in the previous method modalities; or certainly, it can execute, by combining the first way and the second way, the method executed by the SN or the MN in the previous method modalities.
    [00192] The processing element here is the same as in the previous description and can be a general purpose processor, for example, a central processing unit (Central Processing Unit, CPU), or it can be configured as one or more integrated circuits for the execution of the previous method, for example, one or more integrated circuits of
    Petition 870190111972, of 11/01/2019, p. 87/100
    82/85 application-specific integrated circuit, ASIC, or one or more microprocessors (digital signal processor, DSP), or one or more arrays of programmable field gates (Field-Programmable Gate Array, FPGA).
    [00193] The storage element can be a memory or it can be a collective name for a plurality of storage elements.
    [00194] With reference to Figure 16, Figure 16 is a schematic structural diagram of a terminal according to an embodiment of this application. The terminal can be the terminal in the previous mode, configured to implement operations of the terminal in the previous mode. As shown in Figure 16, the terminal includes: a processing element 1610, a storage element 1620 and a transceiver element 1630. The transceiver element 1630 can be connected to an antenna. In a downlink direction, the transceiver element 1630 receives, via the antenna, information sent by a base station, and sends the information to the processing element 1610 for processing. In an uplink direction, processing element 1610 processes data from the terminal, and sends data from the terminal to the base station via transceiver element 1630.
    [00195] The storage element 1620 is configured to store a program to implement the previous method modality. Processing element 1610 invokes the program to perform an operation in the previous method mode.
    [00196] In another implementation, the units shown in Figure 14 can be configured as one or more processing elements to implement a method performed by
    Petition 870190111972, of 11/01/2019, p. 88/100
    83/85 anterior terminal. These processing elements are arranged on a terminal circuit board. The processing elements described herein can be an integrated circuit, for example, one or more ASICs, or one or more DSPs, or one or more FPGAs. These integrated circuits can be integrated to form a chip.
    [00197] For example, the units shown in Figure 14 can be integrated and implemented as a system on a chip (system-on-a-chip, SOC). For example, the terminal includes a SOC chip, configured to implement the previous method. The chip can be integrated with processing element 1610 and storage element 1620, and processing element 1610 invokes the program stored in storage element 1620 to implement the previous method or functions of the units shown in Figure 14. Alternatively, the chip can be integrated with at least one integrated circuit, to implement the previous method or functions of the units shown in Figure 14. Alternatively, the previous implementations can be combined, where the functions of some units are implemented by the processing element to be invoked a program, and functions of some units are implemented by an integrated circuit.
    [00198] Regardless of the ways used, the apparatus of previous configuration includes at least one processing element and a storage element, where the at least one processing element is configured to execute the method provided in the previous method modalities. The processing element can execute, in a first way, that is, by executing a program
    Petition 870190111972, of 11/01/2019, p. 89/100
    84/85 stored in the storage element, some or all of the steps in the previous method modalities; or it can be executed, in a second way, that is, using a logic integrated circuit to the hardware in an element and instructions of the processor, some or all the steps in the previous method modalities; or certainly, it can execute, by combining the first and second ways, the method provided in the previous method modalities.
    [00199] The processing element here is the same as in the previous description and can be a general purpose processing element, for example, a central processing unit (Central Processing Unit, CPU), or it can be configured as one or more circuits integrated to implement the previous method, for example, one or more application specific integrated circuits (ApplicationSpecific Integrated Circuit, ASIC), or one or more microprocessors (digital signal processor, DSP), or one or more arrays of programmable field gates ( FieldProgrammable Gate Array, FPGA).
    [00200] The storage element can be a memory, or it can be a collective name for a plurality of storage elements.
    [00201] A person with common knowledge in the technique can understand that all or some of the steps of the method modalities can be implemented by a program that instructs the relevant hardware. The program can be stored on a computer-readable storage medium. When the program is executed, the steps of the method modalities are executed. The storage medium includes: various media that can store program code, such as a ROM, a
    Petition 870190111972, of 11/01/2019, p. 90/100
    85/85
    RAM, a magnetic disk, or an optical disk.
    权利要求:
    Claims (60)
    [1]
    AMENDED CLAIMS
    1. Configuration method, characterized by the fact that it is applied to a communications system, in which the communications system comprises a master node and a secondary node that jointly provide a service for a terminal, and the method comprises:
    generate (S510, S620, S720), by the secondary node, configuration information for a signaling radio carrier (SRB), in which the SRB is used to transmit a radio resource control (RRC) message between the secondary node and the terminal;
    send (S520, S630, S730), through the secondary node, the SRB configuration information to the master node, where the configuration information for the SRB is sent to the terminal through the master node; and receive (S560, S570, S670, S770), by the secondary node, a result of configuring the SRB through the terminal for using the configuration information for the SRB.
    [2]
    2. Method, according to claim 1, characterized by the fact that it also comprises:
    receive (S501), by the secondary node, indication information from the master node, where the indication information is used to instruct the secondary node to establish the SRB or is used to instruct the secondary node to generate the configuration information for the SRB; and the generation (S510, S620, S720), by the secondary node, of configuration information for an SRB comprises:
    generate (S510, S620, S720), by the secondary node, the configuration information for the SRB based on the indication information.
    Petition 870190094293, of 9/20/2019, p. 40/58
    2/19
    [3]
    3. Method, according to claim 1, characterized by the fact that the generation (S510, S620, S720), by the secondary node, of configuration information for an SRB comprises:
    generate (S620), by the secondary node, the configuration information for the SRB when the secondary node receives (S610) an add request message from the master node, in which the add request message is used to request the add secondary node.
    [4]
    4. Method, according to claim 1 or 3, characterized by the fact that the secondary node triggers the configuration or establishment of the SRB.
    [5]
    Method according to any one of claims 1 to 4, characterized in that the configuration information for the SRB comprises at least one of the following information: an SRB identifier, a radio link control layer configuration (RLC) of the SRB, a logical channel configuration, and an SRB security parameter.
    [6]
    6. Method according to any one of claims 1 to 5, characterized by the fact that it further comprises:
    receiving, by the secondary node, security information used for the SRB of the secondary node from the master node, where the security information comprises at least one of a security key and information about a security algorithm.
    [7]
    Method according to any one of claims 1 to 6, characterized by the fact that it further comprises:
    receive, by the secondary node, a group of keys from the master node, where the group of keys comprises a
    Petition 870190094293, of 9/20/2019, p. 41/58
    3/19 plurality of keys; and select, by the secondary node, a key from the key group when updating a key.
    [8]
    8. Method according to any one of claims 1 to 7, characterized by the fact that it further comprises:
    receiving (S1110), by the secondary node, measurement configuration information from the master node, where the measurement configuration information is used to configure a condition to trigger the secondary node to send a measurement result to the master node; and send (S1130), through the secondary node, a measurement result satisfying the condition to the master node.
    [9]
    9. Method according to any one of claims 1 to 8, characterized by the fact that the sending (S520, S630, S730), by the secondary node, of the SRB configuration information to the master node comprises:
    send, through the secondary node, the SRB configuration information to the master node as an RRC container.
    [10]
    10. Method, according to claim 9, characterized by the fact that the container is transported in an acknowledgment message sent by the secondary node to the master node, and the acknowledgment message is a response message for the request message used to request the addition of a secondary node.
    [11]
    11. Method according to any one of claims 1 to 10, characterized by the fact that it further comprises:
    send, through the secondary node, an RRC connection reconfiguration message to the terminal; and receive, by the secondary node, a configuration failure notification from the master node when the configuration of the
    Petition 870190094293, of 9/20/2019, p. 42/58
    4/19 RRC connection reset message failed.
    [12]
    12. Configuration device, characterized by the fact that it is applied to a secondary node in a communications system, in which the communications system comprises a master node and the secondary node that together provide a service for a terminal, the device comprises a first communications unit (1210) and a second communications unit (1220), the first communications unit (1210) is configured to control communication between the secondary node and the master node, the second communications unit (1220) is configured to control communication between the secondary node and the terminal, and the device also comprises:
    a generation unit (1230), configured to generate configuration information for a signaling radio carrier (SRB), where the SRB is used to transmit a radio resource control (RRC) message between the secondary node and the terminal, where the first communications unit (1210) is configured to send the SRB configuration information to the master node, where the configuration information to the SRB is sent to the terminal through the master node; and the first communications unit (1210) or the second communications unit (1220) is configured to receive a result of configuring the SRB through the terminal by using the configuration information for the SRB.
    [13]
    13. Apparatus according to claim 12, characterized by the fact that the first communications unit (1210) is further configured to receive indication information from the master node, where the indication information is used to instruct the node
    Petition 870190094293, of 9/20/2019, p. 43/58
    5/19 secondary to establish the SRB or is used to instruct the secondary node to generate the configuration information for the SRB; and the generating unit (1230) is configured to generate the configuration information for the SRB based on the indication information.
    [14]
    14. Apparatus according to claim 12, characterized by the fact that the first communications unit (1210) is further configured to receive an add request message from the master node, where the add request message is used to request the addition of a secondary node; and the generation unit (1230) is configured to generate configuration information for the SRB when the first communications unit (1210) receives the add request message.
    [15]
    15. Apparatus according to claim 12 or 14, characterized by the fact that it further comprises:
    a unit configured to trigger the SRB configuration or establishment.
    [16]
    16. Apparatus according to any one of claims 12 to 15, characterized in that the configuration information for the SRB comprises at least one of the following information: an SRB identifier, a radio link control layer configuration (RLC) of the SRB, a logical channel configuration, and an SRB security parameter.
    [17]
    17. Apparatus according to any one of claims 12 to 16, characterized by the fact that the first communications unit (1210) is further configured
    Petition 870190094293, of 9/20/2019, p. 44/58
    6/19 to:
    receiving security information used for the secondary node's SRB from the master node, where the security information comprises at least one of a security key and information about a security algorithm.
    [18]
    18. Apparatus according to any one of claims 12 to 17, characterized by the fact that the first communications unit (1210) is further configured to receive a group of keys from the master node, in which the group of keys comprises a plurality of keys; and the device further comprises:
    a selection unit (1250), configured to select a key from the key group when the secondary node updates a key.
    [19]
    19. Apparatus according to any one of claims 12 to 18, characterized in that the first communications unit (1210) is further configured to receive measurement configuration information from the master node, in which the configuration information measurement is used to configure a condition to trigger the secondary node to send a measurement result to the master node; and the first communications unit (1210) is further configured to send a measurement result satisfying the condition to the master node.
    [20]
    20. Apparatus according to any of claims 12 to 19, characterized in that the first communications unit (1210) sends the configuration information to the SRB to the master node as an RRC container.
    Petition 870190094293, of 9/20/2019, p. 45/58
    7/19
    [21]
    21. Apparatus according to claim 20, characterized by the fact that the container is transported in an acknowledgment message sent by the first communications unit (1210) to the master node, and the acknowledgment message is a reply message to the request message used to request the addition of a secondary node.
    22. Apparatus, according to any of the
    claims 12 to 21, characterized in that the second communications unit (1220) is further configured to send an RRC connection reconfiguration message to the terminal; and the first communications unit (1210) is still
    configured for receive a failure notification from
    configuration from the master node when the RRC connection reconfiguration message configuration fails.
    23. Method of configuration, characterized by the fact that
    which comprises:
    receive (S530, S640, S740), through a terminal, information
    configuration for a signaling radio carrier (SRB) from a secondary node from a master node, where the SRB is used to transmit a radio resource control (RRC) message between the secondary node and the terminal; and configure (S540, S650, S750), by the terminal, the SRB for using the configuration information for the SRB; and
    send (S550, S570, S660, S760), through the terminal, a
    result of configuring the SRB.
    24. Method, according to claim 23,
    characterized by the fact that shipping (S550, S570, S660,
    Petition 870190094293, of 9/20/2019, p. 46/58
    8/19
    S760), through the terminal, of a result of configuring the SRB comprises:
    send (S570), through the terminal, the result of the secondary node directly; or send (S550, S660, S760), through the terminal, the result to the secondary node through the master node.
    [22]
    25. Method according to claim 23 or 24, characterized in that the configuration information for the SRB comprises at least one of the following information: an SRB identifier, a radio link control layer (RLC) configuration ) of the SRB, a logical channel configuration, and an SRB security parameter.
    [23]
    26. Method according to any one of claims 23 to 25, characterized by the fact that it further comprises:
    receive, by the terminal, a count value from the secondary node, and update a key based on the count value.
    [24]
    27. Method according to any of claims 23 to 26, characterized by the fact that it further comprises:
    receive, by the terminal, an RRC connection reconfiguration message from the secondary node; and when the terminal fails to perform the reconfiguration corresponding to the RRC connection reconfiguration message, it will operate from the terminal based on the configuration before the RRC connection reconfiguration message is received.
    [25]
    28. Method, according to claim 27, characterized by the fact that the terminal does not trigger the RRC connection reestablishment.
    [26]
    29. The method of claim 27 or 28,
    Petition 870190094293, of 9/20/2019, p. 47/58
    9/19 characterized by the fact that it also comprises:
    send, through the terminal, a configuration failure notification to the master node.
    [27]
    30. Method according to any one of claims 23 to 29, characterized by the fact that it further comprises:
    receive (S910), by the terminal, a downlink RRC message from the secondary node, in which the downlink RRC message is received by the master node from the secondary node and sent to the terminal, or the downlink RRC message is sent by the secondary node to the terminal; and sending (S920), through the terminal, an uplink RRC message, in which the uplink RRC message is a response message to the downlink RRC message, and a path in which the terminal sends the link RRC message. upstream is the same as the path on which the terminal receives the downlink RRC message.
    [28]
    31. Configuration device, characterized by the fact that it comprises:
    a receiving unit (1410), configured to receive configuration information for a signaling radio carrier (SRB) from a secondary node from a master node, where the SRB is used to transmit a resource control message from radio (RRC) between the secondary node and the device;
    a configuration unit (1430), configured to configure the SRB by using the configuration information for the SRB; and a sending unit (1420), configured to send a result of configuring the SRB.
    [29]
    32. Apparatus according to claim 31,
    Petition 870190094293, of 9/20/2019, p. 48/58
    10/19 characterized by the fact that the sending unit (1420) is configured to send the result to the secondary node directly; or send the result to the secondary node via the master node.
    [30]
    33. Apparatus according to claim 31 or 32, characterized in that the configuration information for the SRB comprises at least one of the following information: an SRB identifier, a radio link control layer (RLC) configuration ) of the SRB, a logical channel configuration, and an SRB security parameter.
    [31]
    34. Apparatus according to any one of claims 31 to 33, characterized in that the receiving unit (1410) is further configured to:
    receive a count value from the secondary node, where a key is updated based on the count value.
    [32]
    35. Apparatus according to any one of claims 31 to 34, characterized in that the receiving unit (1410) is further configured to receive an RRC connection reconfiguration message from the secondary node; and the configuration unit (1430) is further configured to:
    perform reconfiguration corresponding to the RRC connection reconfiguration message, in which when reconfiguration fails, the device works based on the configuration before the RRC connection reconfiguration message is received.
    [33]
    36. Apparatus according to claim 35, characterized by the fact that the configuration unit (1430) does not trigger the RRC connection reestablishment.
    [34]
    37. Apparatus according to claim 35 or 36,
    Petition 870190094293, of 9/20/2019, p. 49/58
    11/19 characterized by the fact that the sending unit (1420) is still configured to send a configuration failure notification to the master node.
    [35]
    38. Apparatus according to any of claims 31 to 37, characterized in that the receiving unit (1410) is further configured to:
    receiving a downlink RRC message from the secondary node, wherein the downlink RRC message is received by the master node from the secondary node and sent to the device, or the downlink RRC message is sent by the secondary node to the device; and the sending unit (1420) is further configured to:
    sending an uplink RRC message, wherein the uplink RRC message is a response message to the uplink RRC message, and a path in which the sending unit (1420) sends the uplink RRC message is the same to the path on which the receiving unit (1410) receives the downlink RRC message.
    [36]
    39. Configuration method, characterized by the fact that it is applied to a communications system, in which the communications system comprises a master node and a secondary node that jointly provide a service for a terminal, and the method comprises:
    receive (S520, S630, S730), by the master node, configuration information for a signaling radio carrier (SRB) from the secondary node, where the SRB is used to transmit a radio resource control message (RRC ) between the secondary node and the terminal;
    send (S530, S640, S740), through the master node, the SRB configuration information to the terminal;
    Petition 870190094293, of 9/20/2019, p. 50/58
    12/19 receive (S550, S660, S760), by the master node, a result of configuring the SRB through the terminal for using the configuration information for the SRB; and send (S560, S670, S770), through the master node, the result to the secondary node.
    [37]
    40. Method according to claim 39, characterized by the fact that the method further comprises:
    send (S501), through the master node, indication information to the secondary node, where the indication information is used to instruct the secondary node to establish the SRB or is used to instruct the secondary node to generate the configuration information for the SRB; or send (S610), through the master node, an add request message to the secondary node, where the add request message is used to request the addition of a secondary node, and the configuration information for the secondary node's SRB is generated by the secondary node when the secondary node is requested to be added.
    [38]
    41. Method according to claim 39 or 40, characterized in that the configuration information for the SRB comprises at least one of the following information: an SRB identifier, a radio link control layer (RLC) configuration ) of the SRB, a logical channel configuration, and an SRB security parameter.
    [39]
    42. Method according to any one of claims 39 to 41, characterized by the fact that the method further comprises:
    send, through the master node, security information used for the SRB from the secondary node to the secondary node,
    Petition 870190094293, of 9/20/2019, p. 51/58
    13/19 where security information comprises at least one security key and information about a security algorithm.
    [40]
    43. Method according to any one of claims 39 to 42, characterized by the fact that it further comprises:
    send, by the master node, a group of keys to the secondary node, where the group of keys comprises a plurality of keys, so that the secondary node selects a key from the group of keys when updating a key.
    [41]
    44. Method according to any one of claims 39 to 43, characterized by the fact that it further comprises:
    send (S1110) measurement configuration information to the secondary node, where the measurement configuration information is used to configure a condition to trigger the secondary node to send a measurement result to the master node; and receiving (S1130) a measurement result satisfying the condition from the secondary node.
    [42]
    45. Method according to any of the claims
    39 to 44, characterized by the fact that the configuration information for the SRB is an RRC container, and the sending (S530, S640, S740), by the master node, of the configuration information to the SRB to the SRB to the terminal comprises:
    forward, through the master node, the RRC container to the terminal without analyzing the RRC container.
    [43]
    46. Method according to any one of claims 39 to 45, characterized by the fact that it further comprises:
    when the terminal fails to perform the configuration of an RRC connection reconfiguration message sent by
    Petition 870190094293, of 9/20/2019, p. 52/58
    14/19 secondary node, receive, by the master node, a notification of configuration failure from the terminal; and notify, through the master node, the secondary node that the configuration fails.
    [44]
    47. Configuration device, characterized by the fact that it is applied to a master node in a communications system, where the communications system comprises the master node and a secondary node that jointly provide a service for a terminal, and the device comprises :
    a first receiving unit (1310), configured to receive configuration information for a signaling radio carrier (SRB) from the secondary node, where the SRB is used to transmit a radio resource control (RRC) message between the secondary node and the terminal;
    a second sending unit (1340), configured to send the configuration information to the SRB to the terminal;
    a second receiving unit (1330), configured to receive a result of configuring the SRB by the terminal for using the configuration information for the SRB; and a first sending unit (1320), configured to send the result to the secondary node.
    [45]
    48. Apparatus according to claim 47, characterized by the fact that the first sending unit (1310) is further configured to:
    send referral information to the secondary node, where referral information is used to instruct the secondary node to establish the SRB or is used to instruct the secondary node to generate the configuration information for the
    Petition 870190094293, of 9/20/2019, p. 53/58
    15/19
    SRB; or send an add request message to the secondary node, where the add request message is used to request the addition of a secondary node, and the configuration information for the secondary node's SRB is generated by the secondary node when the node secondary is requested to be added.
    [46]
    49. Apparatus according to claim 47 or 48, characterized in that the configuration information for the SRB comprises at least one of the following information: an SRB identifier, a radio link control layer (RLC) configuration ) of the SRB, a logical channel configuration, and an SRB security parameter.
    [47]
    50. Apparatus according to any of claims 47 to 49, characterized in that the first sending unit (1320) is further configured to:
    sending security information used for the SRB from the secondary node to the secondary node, where the security information comprises at least one of a security key and information about a security algorithm.
    [48]
    51. Apparatus according to any one of claims 47 to 50, characterized in that the first sending unit (1320) is further configured to:
    send a group of keys to the secondary node, where the group of keys comprises a plurality of keys, so that the secondary node selects a key from the group of keys when updating a key.
    [49]
    52. Apparatus according to any of claims 47 to 51, characterized by the fact that the
    Petition 870190094293, of 9/20/2019, p. 54/58
    16/19 the first sending unit (1320) is further configured to: send measurement configuration information to the secondary node, where the measurement configuration information is used to configure a condition to trigger the secondary node to send a result of measurement for the master node; and the first receiving unit (1310) is further configured to:
    receive a measurement result satisfying the condition from the secondary node.
    [50]
    53. Apparatus according to any of claims 47 to 52, characterized in that the configuration information for the SRB is an RRC container, and the second shipping unit (1340) forwards the RRC container to the terminal without analyzing the RRC container.
    [51]
    54. Apparatus according to any of claims 47 to 53, characterized by the fact that when the terminal fails to perform the configuration of an RRC connection reconfiguration message sent by the secondary node;
    the second receiving unit (1330) is further configured to receive a notification of configuration failure from the terminal; and the first sending unit (1320) is configured to notify the secondary node that the configuration fails.
    [52]
    55. Configuration apparatus, characterized by the fact that it comprises at least one processing element and at least one storage element, wherein the at least one storage element is configured to store a program and data, and the at least one element The processing method is configured to execute the method as defined in any of claims 1 to 11.
    Petition 870190094293, of 9/20/2019, p. 55/58
    17/19
    [53]
    56. Configuration apparatus, characterized by the fact that it comprises at least one processing element and at least one storage element, wherein the at least one storage element is configured to store a program and data, and the at least one element The processing method is configured to execute the method as defined in any one of claims 23 to 30.
    [54]
    57. Configuration apparatus, characterized by the fact that it comprises at least one processing element and at least one storage element, wherein the at least one storage element is configured to store a program and data, and the at least one element The processing method is configured to execute the method as defined in any one of claims 39 to 46.
    [55]
    58. Computer program, characterized by the fact that when executed by a processor, the program is used to execute the method as defined in any one of claims 1 to 11, 23 to 30 and 39 to 46.
    [56]
    59. Computer-readable storage medium, characterized by the fact that it comprises a program, in which, when executed by a processor, the program is used to execute the method as defined in any one of claims 1 to 11, 23 to 30 and 39 to 46.
    [57]
    60. Radio resource control (RRC) message transmission method, characterized by the fact that it comprises:
    receiving (S910), by a terminal, a downlink RRC message from a secondary node, in which the downlink RRC message is received by a master node from the secondary node and sent to the terminal, or the message
    Petition 870190094293, of 9/20/2019, p. 56/58
    18/19
    Downlink RRC is sent by the secondary node to the terminal; and send (S920), through the terminal, an uplink RRC message, in which the uplink RRC message is a response message to the uplink RRC message, and a path in which the terminal sends the link RRC message. upstream is the same as the path on which the terminal receives the downlink RRC message.
    [58]
    61. Radio resource control (RRC) message transmission apparatus, characterized by the fact that it comprises:
    a receiving unit (1410) configured to receive a downlink RRC message from a secondary node, where the downlink RRC message is received by a master node from the secondary node and sent to a terminal, or the message Downlink RRC is sent by the secondary node to a terminal; and a sending unit (1420) configured to send an uplink RRC message, wherein the uplink RRC message is a response message to the uplink RRC message, and a path in which the terminal sends the message. Uplink RRC is the same as a path on which the terminal receives the downlink RRC message.
    [59]
    62. Radio resource control (RRC) message transmission apparatus, characterized by the fact that it comprises at least one processing element and at least one storage element, wherein the at least one storage element is configured to store a program and data, and the at least one processing element
    Petition 870190094293, of 9/20/2019, p. 57/58
    19/19
    is configured to run the method like defined in claim 60.63. Medium of storage readable by computer, featured by the fact that comprises a program in
    that when executed by a processor, the program is used to execute the method as defined in claim 60.
    [60]
    64. System, characterized by the fact that it comprises a master node and a secondary node that jointly provide a service for a terminal, wherein the secondary node comprises the apparatus as defined in any of claims 12 to 22, and 55, and the The master node comprises the apparatus as defined in any of claims 47 to 54 and 57.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112019019652A2|2020-04-22|configuration method and apparatus, rrc message transmission method and apparatus, computer-readable storage medium, and system
    JPWO2019030981A1|2020-07-30|Radio access network node, core network node, and radio terminal and methods thereof
    JP6741178B2|2020-08-19|Radio access network node and radio terminal and methods thereof
    US20190182883A1|2019-06-13|Cell configuration method and device
    US10785824B2|2020-09-22|Information processing method and related apparatus
    JP2017514367A|2017-06-01|Bearer management apparatus, method, and communication system
    JP6733744B2|2020-08-05|Source base station method and wireless terminal method
    BR112020022142A2|2021-01-26|maintenance of communication and signaling interfaces through a network function transition
    US11109263B2|2021-08-31|Data transmission method and data transmission apparatus
    JP6243067B2|2017-12-06|Base station and method
    BR112019026671A2|2020-06-30|communication method, communication devices, computer program storage medium and communication system
    US20200100102A1|2020-03-26|Method and apparatus for supporting security for cu-cp and cu-up separation in wireless communication system
    US10798766B2|2020-10-06|Multi-connectivity communication method and device
    WO2015161575A1|2015-10-29|Method, base station, mobile management entity, and system for reporting location of user terminal
    WO2016101617A1|2016-06-30|Security information processing method in switching procedure, access gateway, and base station
    JP2018174597A|2018-11-08|Bearer management device, method and communication system
    WO2021204022A1|2021-10-14|Measurement method and apparatus
    CN113543191A|2021-10-22|Communication method and communication device
    同族专利:
    公开号 | 公开日
    RU2019133391A3|2021-08-30|
    RU2019133391A|2021-04-23|
    EP3598823A1|2020-01-22|
    CA3057209A1|2018-09-27|
    JP6950140B2|2021-10-13|
    US20200022209A1|2020-01-16|
    KR102295892B1|2021-08-31|
    EP3598823B1|2021-08-25|
    WO2018171583A1|2018-09-27|
    KR20190131057A|2019-11-25|
    JP2020511846A|2020-04-16|
    RU2763784C2|2022-01-11|
    CN108633018A|2018-10-09|
    EP3598823A4|2020-03-18|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    CN103139911B|2011-11-25|2016-10-05|华为技术有限公司|Realize the method for carrier aggregation, base station and subscriber equipment|
    KR102040883B1|2012-08-23|2019-11-05|인터디지탈 패튼 홀딩스, 인크|Operating with multiple schedulers in a wireless system|
    WO2014101140A1|2012-12-28|2014-07-03|华为技术有限公司|Coordinating communication method, user equipment, and base station|
    EP2946503B1|2013-01-16|2018-10-03|LG Electronics Inc.|Method and apparatus for transmitting indication in wireless communication system|
    US20150043492A1|2013-08-12|2015-02-12|Electronics And Telecommunications Research Institute|Method for providing dual connectivity in wireless communication system|
    CN104618927B|2013-11-01|2019-04-19|电信科学技术研究院|Method for reconfiguration, user equipment and the more evolved base stations of more evolved base stations|
    US10039086B2|2013-11-11|2018-07-31|Electronics And Telecommunications Research Institute|Communication method and apparatus in network environment where terminal may have dual connectivity to multiple base stations|
    US9713044B2|2014-01-30|2017-07-18|Sharp Kabushiki Kaisha|Systems and methods for dual-connectivity operation|
    CN105917727B|2014-01-30|2019-12-13|夏普株式会社|User equipment, evolved node B and method thereof|
    US20170019945A1|2014-03-21|2017-01-19|Nokia Solutions And Networks Oy|Dual Connectivity Re-Establishment|
    CN106576381B|2014-08-08|2020-10-02|Lg电子株式会社|Method and apparatus for notifying service release for dual connectivity in wireless communication system|
    EP3041310B1|2014-12-23|2018-09-26|HTC Corporation|Methods of handling simultaneous communications and related communication devices|
    KR102106134B1|2015-05-15|2020-05-04|주식회사 케이티|Methods for configuring wireless connection of user equipment and Apparatuses thereof|
    CN106304403A|2015-06-10|2017-01-04|电信科学技术研究院|A kind of multi-link method for building up and relevant device|CN109391362A|2017-08-11|2019-02-26|中兴通讯股份有限公司|A kind of signal transmission method and device|
    US10708972B2|2017-08-17|2020-07-07|Telefonaktiebolaget Lm Ericsson |Radio link management in a split RAN architecture|
    CN112205055A|2018-09-28|2021-01-08|Oppo广东移动通信有限公司|Information transmission method and device, terminal and network equipment|
    CN111148164B|2018-11-02|2021-05-28|电信科学技术研究院有限公司|Data forwarding method and device, master base station and slave base station|
    CN111194032B|2018-11-14|2021-08-13|华为技术有限公司|Communication method and device thereof|
    WO2020147120A1|2019-01-18|2020-07-23|Qualcomm Incorporated|Early measurement reporting|
    WO2020164367A1|2019-02-12|2020-08-20|电信科学技术研究院有限公司|Parameter configuration method and apparatus|
    BR112020020055A2|2019-02-13|2021-01-05|Guangdong Oppo Mobile Telecommunications Corp., Ltd.|METHOD AND APPLIANCE FOR CARRIER CONFIGURATION|
    CN111436163B|2019-03-28|2022-03-01|维沃移动通信有限公司|Configuration negotiation method and network node|
    CN111866963B|2019-04-28|2021-12-31|华为技术有限公司|Communication method, communication device, computer storage medium, and communication system|
    WO2020243976A1|2019-06-07|2020-12-10|Qualcomm Incorporated|Method and apparatus for method to improve user experience for dual connectivity devices|
    CN112087816A|2019-06-14|2020-12-15|华为技术有限公司|Method for determining safety activation state and related product|
    CN112399528A|2019-08-15|2021-02-23|华为技术有限公司|Communication method, device, equipment and storage medium based on dual-connection configuration|
    WO2021030984A1|2019-08-16|2021-02-25|华为技术有限公司|Configuration method and apparatus, and computer readable storage medium and system|
    WO2022021413A1|2020-07-31|2022-02-03|Oppo广东移动通信有限公司|Key generation method and apparatus, and terminal device and network device|
    法律状态:
    2021-10-19| B350| Update of information on the portal [chapter 15.35 patent gazette]|
    优先权:
    申请号 | 申请日 | 专利标题
    CN201710179753.7A|CN108633018A|2017-03-23|2017-03-23|Configuration method, apparatus and system|
    PCT/CN2018/079627|WO2018171583A1|2017-03-23|2018-03-20|Configuration method, apparatus and system|
    [返回顶部]